Apparatuses, methods, and computer-readable medium for communication in a wireless local area network

ABSTRACT

Various aspects related to various apparatuses, methods, and computer-readable medium are described herein. Some aspects may enable an apparatus to protect downlink (DL) communication(s). Some aspects may enable an apparatus to perform DL communication(s). Some aspects may enable an apparatus to communicate regarding uplink (UL) communication(s). Some aspects may enable an apparatus to perform operation(s) related to an allocation vector. Some aspects may enable an apparatus to perform operation(s) related to random access. Some aspects may enable an apparatus to perform UL communication(s). The written description and appended drawings provide detailed descriptions regarding these and many other aspects.

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present application claims the benefit of and right of priority toU.S. patent application Ser. No. 15/322,117, titled “APPARATUSES,METHODS, AND COMPUTER-READABLE MEDIUM FOR COMMUNICATION IN A WIRELESSLOCAL AREA NETWORK,” filed Dec. 25, 2016, which claims the benefit ofand right of priority to International Patent Cooperation Treaty (PCT)Patent Application No. PCT/US2016/042179, titled “APPARATUSES, METHODS,AND COMPUTER-READABLE MEDIUM FOR COMMUNICATION IN A WIRELESS LOCAL AREANETWORK,” filed Jul. 14, 2016, which claims the benefit of and right ofpriority to U.S. Provisional Patent Application No. 62/193,497, titled“APPARATUSES, METHODS, AND COMPUTER-READABLE MEDIUM FOR COMMUNICATION,”filed Jul. 16, 2015, U.S. Provisional Patent Application No. 62/219,639,titled “APPARATUSES, METHODS, AND COMPUTER-READABLE MEDIUM FORCOMMUNICATION,” filed Sep. 16, 2015, and U.S. Provisional PatentApplication No. 62/254,153, titled “APPARATUSES, METHODS, ANDCOMPUTER-READABLE MEDIUM FOR COMMUNICATION,” filed Nov. 11, 2015, theentirety of all of which is hereby expressly incorporated by referenceherein.

TECHNICAL AREA

The present disclosure, generally, pertains to communication and, morespecifically, to apparatuses, methods, and computer-readable medium forcommunication in a wireless local area network.

BACKGROUND

A wireless local area network (WLAN) may refer to a network thatwirelessly connects two or more devices in a coverage area. A WLAN canbe deployed in many types of environments, such as residential,commercial, and/or public. Devices can be moved around in the coveragearea of the WLAN while maintaining a wireless connection. A WLAN may beutilized to access a local intranet and/or the Internet. Devices in aWLAN can communicate with each other using various procedures.Improvements to such procedures may enable relatively faster downloadand/or upload of information, relatively less latency, and/or relativelyless power consumption, which may improve the overall user experience.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptual diagram illustrating a non-limiting example of atleast one wireless local area network according to some aspects of thepresent disclosure.

FIG. 2 is a timing diagram illustrating non-limiting examples of variouscommunications between an access point (AP) and various stations (STAs)according to some aspects of the present disclosure.

FIG. 3 illustrates non-limiting examples of diagrams associated withsome aspects of the present disclosure.

FIG. 4 is a flow diagram illustrating non-limiting examples of someaspects of the present disclosure.

FIG. 5 is a block diagram illustrating a non-limiting example of an APaccording to some aspects of the present disclosure.

FIG. 6 is a block diagram illustrating a non-limiting example of a STAaccording to some aspects of the present disclosure.

The drawings are not intended to limit the scope of the presentdisclosure nor any aspect of the claims. The drawings are providedsolely to illustrate a few aspects that may be described in greaterdetail throughout the present disclosure. Accordingly, some aspectsdescribed throughout the present disclosure may not be illustrated inthe drawings.

DETAILED DESCRIPTION

A wireless local area network (WLAN) may have one or more access points(APs) and/or one or more stations (STAs). In some aspects, the term(s)‘AP,’ ‘apparatus’ (e.g., an apparatus of an AP), and/or‘computer-readable medium’ (e.g., a computer-readable medium of an AP)may be, may reside within, and/or may refer to a router, a base station,a transmitter, a base transceiver station, a node, a radio base station,a radio transceiver, a network, a basic service set (BSS), an extendedservice set, a computing device, a user equipment (UE), a phone, a meshnode, a relay, a peer, a device, one or more software modules, one ormore computer-executable code/instructions, one or morecomputer-readable medium, one or more memory, one or more processor, oneor more hardware components, one or more circuits or modules, anycombination of any one or more of the foregoing items, and/or any othersuitable term(s), any one or more of which may be suitable forperforming any one or more of the methods, operations, steps, functions,features, and/or other aspects described herein.

In some aspects, the term(s) ‘STA,’ apparatus' (e.g., an apparatus of anSTA), and/or ‘computer-readable medium’ (e.g., a computer-readablemedium of an STA) may be, may reside within, and/or may refer to alaptop computer, a mobile phone, a cellular phone, a mobile station, aUE, a phone, a handset device, a subscriber station, a mobile unit, awireless device, a smartphone, a remote device, a tablet device, adesktop computer, a terminal, a mobile client, a mesh node, a relay, apeer, a netbook, a notebook, a computer display, a satellite radio, aprojector, a payment device, a display device, a global positioningsystem device, a multimedia device, a game console, a camera, avideo-recorder, an entertainment device, a wearable computing device,glasses, a watch, a health/fitness tracker, an appliance, a transportvehicle, a car, a sensor, a fax/facsimile machine, a printer, a scanner,one or more software modules, one or more computer-executablecode/instructions, one or more computer-readable medium, one or morememory, one or more processor, one or more hardware components, one ormore circuits or modules, any combination of any one or more of theforegoing items, and/or any other suitable term(s), any one or more ofwhich may be suitable for performing any one or more of the methods,operations, steps, functions, features, and/or other aspects describedherein.

An AP may be configured to communicate downlink (DL) signals to one ormore other apparatuses, such as one or more STAs. An STA may beconfigured to communicate uplink (UL) signals to one or more otherapparatuses, such as one or more APs and/or one or more other STAs.Generally, a transmission from an AP to one or more STAs may becharacterized as DL, and a transmission from an STA to one or more APsmay be characterized as UL. DL may refer to any communication initiatedby, originated at, communicated from, generated by, and/or transmittedby an AP and destined for, intended for, and/or received by an STA. ULmay refer to any communication initiated by, originate at, communicatedfrom, generated by, and/or transmitted by an STA and destined for,intended for, and/or received by an AP.

FIG. 1 is a conceptual diagram 100 illustrating a non-limiting exampleof at least one WLAN according to some aspects of the presentdisclosure. In the example illustrated in FIG. 1, AP₁ 112 has a coveragearea 110 that at least partially overlaps with a coverage area 140 ofAP₂ 142. The coverage area 110 of AP₁ 112 includes STA₁ 114, STA₂ 116,and STA₄ 118. The coverage area of AP₂ 142 includes STA₁ 114, STA₃ 144,and STA₅ 146. FIG. 1 illustrates many DL transmissions 122, 126, 152,158 and many UL transmissions 124, 128, 154, 156. Additionally oralternatively, STAs may communicate with each other via peer-to-peertransmissions 130, 132. Additional details related to the aforementionedtransmissions are provided throughout the present disclosure.

FIG. 2 is a timing diagram 200 illustrating non-limiting examples ofvarious communications between an AP and various STAs according to someaspects of the present disclosure. In some aspects, at time AP₁ 112 maytransmit one or more DL transmission(s) 202, 204 to STA₁ 114, STA₂ 116,respectively. Such DL transmission(s) 202, 204 may be configured tocause STA₁ 114, STA₂ 116 to transmit an UL transmission (e.g., ULtransmission(s) 212, 214, respectively) that may be configured toprotect a DL multiuser transmission (e.g., DL multiuser transmission222). In some aspects, at time T_(ii), STA₁ 114, STA₂ 116 mayrespectively communicate UL transmission(s) 212, 214 to AP₁ 112. Such ULtransmission(s) 212, 214 may be configured to protect a DL multiusertransmission (e.g., DL multiuser transmission 222). Various aspectspertaining to such DL transmission(s) 202, 204 and/or UL transmission(s)212, 214 are provided in greater detail herein (e.g., with reference toFIG. 4).

In some aspects, at time T_(iii), AP₁ 112 may transmit a DL multiusertransmission 222 to STA₁ 114 and STA₂ 116. The DL multiuser transmission222 may include data and/or information destined/intended for aplurality STAs (e.g., STA₁ 114, STA₂ 116). In some aspects, the term‘multiuser’ may be described herein with reference to a transmission (orother similar terms, such as communication, signal, packet, and/or dataunit). A DL multiuser transmission may refer to a transmission thatoriginates at a single transmitter (e.g., apparatus, AP, BSS, node,network, etc.) and includes data and/or information destined/intendedfor a plurality of receivers (e.g., apparatuses, STAs, users, receivers,destinations, etc.). Various aspects pertaining to such DL multiusertransmission(s) 222 are provided in greater detail herein (e.g., withreference to FIG. 4).

In some aspects, at time T_(iv), AP₁ may transmit DL transmission(s)232, 234 to STA₁ 114, STA₂ 116, respectively. In some aspects, the DLtransmission(s) 232, 234 may be different transmissions (e.g., one DLtransmission 232 destined/intended for STA₁ 114, and another DLtransmission 234 destined/intended for STA₂ 116). In some aspects, theDL transmission(s) 222 may refer to a single DL transmission (e.g., asingle DL transmission destined/intended for STA₁ 114 and STA₂ 116). Insome aspects, the DL transmission(s) 232, 234 may be included as a partof another DL transmission(s) (e.g., DL multiuser transmission(s) 222).

In some aspect, the DL transmission(s) 232, 234 may be configured totrigger simultaneous/concurrent UL transmission(s) 262, 264 by aplurality of STAs (e.g., STA₁ 114, STA₂ 116). In some aspects, such DLtransmission(s) 232, 234 may be referred to as an UL transmissionrequest (ULTR). The term ‘ULTR’ may refer to a signal configured totrigger an UL transmission by at least one STA. In some aspects, theULTR may be a signal configured to trigger simultaneous/concurrent ULtransmissions by a plurality of STAs within a period of time afterreceiving the signal. The ULTR may be referred to by various otherterms/phrases (e.g., UL transmission trigger, UL trigger frame, and/orvarious other suitable terms/phrases) without deviating from the scopeof the present disclosure. An ULTR may be characterized as ‘cascading’when another ULTR is planned, scheduled, and/or destined to follow thatULTR. Various aspects pertaining to such DL transmission(s) 232, 234 areprovided in greater detail herein (e.g., with reference to FIG. 4).

In some aspects, at time T_(vii), the simultaneous/concurrent ULtransmissions 262, 264 may include an UL transmission 262 from STA₁ 114to AP₁ 112 simultaneously/concurrently with an UL transmission 264 fromSTA₂ 116 to AP₁ 112. In some aspects, the UL transmission(s) 262, 264may be referred to as UL multiuser transmission(s). UL multiusertransmission(s) may refer to one or more transmissions that originate atdifferent transmitters (e.g., apparatuses, STAs, users, etc.) and eachinclude data and/or information destined/intended for a common/sharedreceiver (e.g., apparatus, AP, node, network, etc.), and suchtransmissions may at least in part occur during a common, concurrent,and/or simultaneous period of time. Various aspects pertaining to suchsimultaneous/concurrent UL transmission(s) 262, 264 are provided ingreater detail herein (e.g., with reference to FIG. 4).

In some aspects, prior to such simultaneous/concurrent UL transmissions262, 264 at time T_(vii), an STA (e.g., STA₁ 114, STA₂ 116), at timeT_(v), may enable various features, operations, functions, and/oraspects 242, 244 related to an allocation vector, such as anetwork/navigation allocation vector (NAV), as described in greaterdetail herein (e.g., with reference to FIG. 4). In some aspects, priorto such simultaneous/concurrent UL transmissions 262, 264 at timeT_(vii), an STA (e.g., STA₁ 114, STA₂ 116), at time T_(vi), may enablevarious features, operations, functions, and/or aspects 252, 254 relatedto random access, as also described in greater detail herein (e.g., withreference to FIG. 4).

FIG. 3 illustrates non-limiting examples of diagrams 300, 350 associatedwith various aspects of the present disclosure. In some aspects, a firstdiagram 300 illustrates non-limiting examples of possible relationshipsbetween a total number of space-time streams (STSs) (included in aframe, packet, and/or data unit) and various possible values in one ormore fields (e.g., field values (FVs)) (that may be included in a frame,packet, and/or data unit). In some aspects, a second diagram 350illustrates non-limiting examples of possible relationships between thenumber (e.g., quantity, numerical quantification, count, amount, size,extent, etc.) of STSs destined/intended for one or more STAsassigned/allocated various possible user position (UP) values in view ofvarious possible FVs (that may be included in a frame, packet, and/ordata unit). Many aspects pertaining to these diagrams 300, 350 areprovided in greater detail herein (e.g., with reference to FIG. 4).

FIG. 4 is a conceptual flow diagram 400 illustrating non-limitingexamples of various features, operations, steps, methods, processes,and/or functions according to some aspects of the present disclosure.Such features, operations, steps, methods, processes, and/or functionsmay be enabled, performed by, reside in, executed by, configured for,and/or otherwise associated with any apparatus described herein, such anAP (e.g., AP₁ 112) and/or an STA (e.g., STA₁ 114).

At block 402, an apparatus may enable aspects related to protecting DLcommunication(s). In some aspects, an AP may transmit and/or an STA mayreceive a transmission configured to cause a plurality of STAs tosimultaneously transmit a signal/transmission that is configured toprotect a DL multiuser transmission to the plurality of STAs. Forexample, referring to FIG. 2, AP₁ 112 may transmit a DL transmission 202to STA₁ 114 and/or a DL transmission 204 to STA₂ 116. Such DLtransmission(s) 202, 204 may be configured to request that STA₁ 114,STA₂ 116 refrain from transmitting signals during a particular period oftime (e.g., at least at time(s) T_(iii), T₁) using a certain channel orresource. In some aspects, in response to such a signal/transmission(e.g., DL transmission(s) 202, 204) and simultaneously/concurrently withanother STA of the plurality of STAs, an STA may transmit and/or an APmay receive a signal/transmission (e.g., UL transmission(s) 212, 214)configured to protect a DL multiuser transmission (e.g., DL multiusertransmission(s) 222) to the plurality of STAs. For example, referring toFIG. 2, STA₁ 114 may transmit an UL transmission 212 at least in partsimultaneously/concurrently with STA₂ 116 transmitting an ULtransmission 214. Such UL transmission(s) 212, 214 may inform AP₁ 112that STA₁ 114, STA₂ 116 will not transmit during that particular periodof time (e.g., at least at time(s) T_(iii), T₁) using that channel orresource, thereby protecting any DL multiuser transmission(s) (e.g., DLmultiuser transmission(s) 222 from AP₁ 112 to STA₁ 114, STA₂ 116) duringthat particular period of time (e.g., at least at time(s) T_(iii),T_(iv)). In some aspects, a time synchronization of the simultaneoustransmission by the plurality of STAs is based on an end time of thereceived signal/transmission. For example, referring to FIG. 2, the ULtransmission(s) 212, 214 may begin after a particular inter-framespacing (e.g., in FIG. 2, time T_(ii) minus time T_(i)) after thecommunication of the DL transmission(s) 202, 204. In some aspects, ascrambling seed associated with the transmitted signal/transmission(e.g., UL transmission(s) 212, 214) configured to protect the DLmultiuser transmission (e.g., DL multiuser transmission(s) 222) issimilar to or the same as a scrambling seed of the receivedsignal/transmission (e.g., DL transmission(s) 202, 204) that caused theplurality of STAs to simultaneously transmit the signal/transmission(e.g., UL transmission(s) 212, 214) configured to protect the DLmultiuser transmission (e.g., DL multiuser transmission(s) 222). Theterm ‘scrambler seed’ may refer to an initial value or state used forscrambling, randomization, and/or encoding an input value. For example,referring to FIG. 2, an initial scrambler state of the DLtransmission(s) 202, 204 may be similar to or the same as an initialscrambler state of the UL transmission(s) 212, 214.

In some configurations, the TX may generate and/or transmit arequest-to-send (RTS) message/signal that solicits simultaneousclear-to-send (CTS) messages/signals from a plurality of RXs. In someconfigurations, the TX may generate and/or transmit a RTS message/signalsimultaneously to a plurality of RXs, and the RTS message/signal may beconfigured to solicit, induce, trigger, and/or otherwise cause thesimultaneous transmission of CTS messages/signals from that sameplurality of RXs. In such configurations, the RX may receive and/ordecode the RTS message/signal and transmit a CTS message/signal at atime indicated in the RTS message/signal. That indicated time may be atthe same time as the time of transmission of CTS message(s)/signal(s) byother RXs (that were intended recipients of the RTS message/signal fromthe TX). In some configurations, the scramble seed associated with thesimultaneous CTS responses may be similar to (or the same as) thescramble seed associated with the RTS message/signal. In someconfigurations, the transmission rate associated with thesimultaneously-transmitted CTS messages/signals may be similar to (orthe same as) the transmission rate associated with the RTSmessage/signal. In some configurations, the transmission rate associatedwith the simultaneously-transmitted CTS messages/signals may be based onthe rate or MCS of the RTS message/signal. In some configurations, thetime synchronization among the RXs is based on the end time of the RTSmessage/signal. In some configurations, the RTS includes anindication/signal that indicates/identifies each of the plurality ofRXs. In some configurations, the CTS message/signal is the same for eachof the plurality of RXs. In some configurations, the CTS message/signalis transmitted at the same start time and/or the same end time by eachof the plurality of RXs as indicated in the RTS message/signal. In someconfigurations, the CTS message/signal is configured to protectmulti-user transmissions from/to the plurality of RXs. In someconfigurations, the RTS message/signal includes an indication/signalindicating that the RTS message/signal is destined for/intended for thatplurality of RXs. In some configurations, the RTS message includes animplicit and/or explicit indicator/signal identifying at least one ofthe MCS, the scrambling seed, transmission rate, or bandwidth (BW) ofthe RTS signal/message. In some configurations, each of the plurality ofRXs generates/transmits the CTS message based on such anindicator/signal. In some configurations, the CTS message/signalcomprises a BW corresponding to the BW of the RTS message/signal.

At block 404, an apparatus may enable aspects related to performing DLcommunication(s). In some aspects, at time T_(iii), an AP may transmitand/or an STA may receive a DL transmission (e.g., DL multiusertransmission(s) 222) comprising a frame, packet, and/or data unitdestined/intended for a plurality of STAs. In some aspects, the DLtransmission (e.g., DL multiuser transmission(s) 222) comprising aframe, packet, and/or data unit destined/intended for a plurality ofSTAs may include a plurality of STSs. For example, one (or more) STS(s)may be destined/intended for STA₁ 114 and another one (or more) STS(s)may be destined/intended for STA₂ 116.

The frame, packet, and/or data unit may include one or more fields. Theterm ‘field(s)’ may refer to any subset, portion, fraction, component,and/or bit of the frame, packet, and/or data unit. In some aspects, anSTA may use a field included in the packet, frame, and/or data unit todetermine a total number of STSs included in the packet, frame, and/ordata unit. For example, as illustrated in a first diagram 300 of FIG. 3,an STA may determine a total number of STSs (e.g., a, b, c, . . . z,which each may represent a non-negative integer value) (included in thepacket, frame, and/or data unit) based on the FV (e.g., A, B, C, . . .Z, which may each represent one or more integer values, one or morecomplex numbers, one or more alphanumeric values, one or more bits, abit string, one or more binary values, one or more hexadecimal values,and/or any other suitable set of one or more values). For instance, ifFV=B, then the total number of STSs included in the frame, packet,and/or data unit is equal to b.

In some aspects, an STA may use the field to select a subset of valuesfrom a set of values indicating a number of STSs destined to each of atleast some of the plurality of STAs. For example, as illustrated in asecond diagram 350 of FIG. 3, the number of STSs associated with each UPmay vary based on the FV. An STA for/to which a packet, frame, and/ordata unit, or at least a portion thereof, is intended/destined may beassigned a UP. A UP may be assigned to one or more STAs. For example, ifFV=B, then the STA may select a subset of values (e.g., B₀, B₁, B₂, B₃,B₄, B₅, . . . , B_(N)) from a set of values (e.g., A₀, A₁, A₂, A₃, A₄,A₅, . . . , A_(N), B₀, B₁, B₂, B₃, B₄, B₅, . . . , B_(N), C₀, C₁, C₂,C₃, C₄, C₅, . . . , C_(N), . . . Z₀, Z₁, Z₂, Z₃, Z₄, Z₅, . . . , Z_(N),wherein each of these value may have any non-negative integer value)indicating the number of STSs destined/intended for each of at leastsome of the plurality of STAs (e.g., STA(s) assigned UP₀, UP₁, UP₂, UP₃,UP₄, UP₅, . . . , UP_(N)). N may correspond to a last value in a seriesof values. Although the example described herein mentions five or morevalues (e.g., N being greater than 5) in each of the set of values, thisis not a limitation of the present disclosure nor any aspect of theclaims, because any of the set of values may have any plurality ofvalues (e.g., two or more values, wherein N is simply greater than 0)without deviating from the scope of the present disclosure.

In some aspects, an STA may determine a value of a UP assigned to theSTA. For example, STA₁ 114 may determine that it is assigned/allocated aparticular UP value, such as UP₃ (e.g., UP_(j), where j=3). Because theframe, packet, and/or data unit may contain a plurality of STSs, not allof which may be destined/intended for a single STA, each of the STAs forwhich that frame, packet, and/or data unit is destined/intended may wishto determine which of the plurality of STSs in the frame, packet, and/ordata unit are destined/intended for that particular STA. In someaspects, an STA may select which of the plurality of STSs in the frame,packet, and/or data unit are destined to the STA by considering a numberof STSs allocated to one or more other STAs each assigned a UP valuethat is different from the UP value assigned to the STA. Ifassigned/allocated UP₃, STA₁ 114 may determine that the number of STSsdestined/intended for that particular STA is B₃ (e.g., B₃-number of STSsare destined/intended for STA₁ 114). However, because the frame, packet,and/or data unit may have more than B₃-number of STSs, STA₁ 114 may wishto determine exactly which of those more-than-B₃-number of STSs is/arethe specific B₃-number of STSs destined/intended for STA₁ 114.

To do so, STA₁ 114 may consider the number of STSs assigned/allocated toone or more other STAs assigned a UP value different from (e.g.,higher/greater than and/or lower/lesser than) UP₃ (e.g., STA(s)assigned/allocated any one or more of UP₀, UP₁, UP₂, UP₄, UP₅, . . . . ,and/or UP_(N)). For example, by considering (i) that B₀-number of STSsare assigned/allocated to STA(s) assigned/allocated UP₀, (ii) thatB₁-number of STSs are assigned/allocated to STA(s) assigned/allocatedUP₁, and/or (iii) that B₂-number of STSs are assigned/allocated toSTA(s) assigned/allocated UP₂, STA₁ 114 (if assigned/allocated UP₃) maydetermine that the starting stream index of the STS(s) destined/intendedfor it begin(s) after the sum of B₀-, B₁-, and B₂-number of STSs (whichare destined/intended for other STA(s) assigned/allocated to UP valuesdifferent from the UP value assigned/allocated to STA₁ 114).

One of ordinary skill in the art will understand that any one or more ofA₀-A_(N) through Z₀-Z_(N) shown in FIG. 3 may have various values,characteristics, relationships, features, requirements, conditions,and/or other suitable attributes without necessarily deviating from thescope of the present disclosure. In some aspects, the number of STSsintended for every STA assigned a higher UP value may never exceed thenumber of STSs intended for the STA. For example, if STA₁ 114 isassigned/allocated UP₃, none of the individual values of B₄, B₅, . . . ,nor B_(N) may exceed the value of B₃. In some aspects, a number of STSsintended for the STA may be greater than or equal to a number of STSsintended for every STA assigned a higher UP value than the UP assignedto the STA. For example, if STA₁ 114 is assigned/allocated UP₃, thevalue of B₃ is greater than or equal to the individual values of B₄, B₅,. . . , and B_(N).

In some aspects, at least one of A₀-A_(N) through Z₀-Z_(N) (shown inFIG. 3) may be variable (e.g., varying, adjustable, non-fixed,comprising a range of two or more possible values, etc.). In someaspects, at least one of the values in the selected subset is variable,and a determination of an exact value for the variable includesconsidering the determined total number of STSs included in the dataframe, packet, and/or data unit. In some aspects, at least one of thevalues in the selected subset is variable, and a determination of anexact value for the variable includes subtracting at least some of theother values in the selected subset of values from the determined totalnumber of STSs included in the data frame, packet, and/or data unit. Forexample, referring to FIG. 3, if FV=B, the selected subset includes B₀,B₁, B₂, B₃, B₄, B₅, . . . , B_(N), and at least one of these values isvariable. For the purpose of illustration but not limitation, it can beassumed that B₃ is variable. As described above, if FV=B, the number ofSTSs included in the frame, packet, and/or data unit is equal to b(e.g., a non-negative integer value). To determine the exact value forB₃ (e.g., a variable, in this example), the value of b is subtracted bythe value of B₀, B₁, B₂, B₄, and B₅ . . . B_(N). For instance, if b=5,B₀=3, B₁=1, B₂=0, B₄=0, and B₅ . . . B_(N)=0, then B₃=5-3−1=1. In someaspects, at least one of the values in the selected subset is variable,and a determination of an exact value for the variable compriseseliminating a possible value if addition of that possible value to theother subset of values generates a sum that exceeds the total number ofSTSs included in the data frame, packet, and/or data unit. For example,referring to FIG. 3, if FV=B, B₀=3, B₁=1, B₂=0, B₄=0, and B₅ . . .B_(N)=0, and B₃ is variable, then the exact value of B₃ may bedetermined by eliminating possible values that cause the sum of thesubset of values (e.g., sum of B₀-B_(N)) to exceed b=5. For instance,the value of B₃=2 can be eliminated because B₃=2 would result in the sumof the subset of values (e.g., sum of B₀-B_(N)) to equal to 6, whichexceeds b=5.

In some configurations, the TX may determine to operate on, search for,and/or probe exclusively a limited number or subset of possiblechannels. For instance, the TX may determine to operate on, search for,and/or probe (e.g., a primary channel) exclusively on non-overlappingchannels. Non-limiting examples of non-overlapping channels may includechannels 1, 6, 11, and/or 14. In some configurations, the TX may do sowhen operating in a particular band (e.g., 2.4 GHz). Non-limitingexamples of (potentially) overlapping channels include one or more ofthe remaining channels. When at least a portion of its frequencyspectrum/range, bandwidth, and/or spectral mask of a first channeloverlaps (or has the potential to overlap) with at least a portion ofthe frequency spectrum/range, bandwidth, and/or spectral mask of atleast a second channel, then the first channel may be characterized asan overlapping channel. In some configurations, the TX may determine tooperate on, search for, and/or probe non-overlapping channels prior tooperating on, searching for, and/or probing on overlapping channels. Insome configurations, the TX may select which channel to operate on,search for, and/or probe based on a likelihood and/or probability of thechannel being a non-overlapping channel. In some configurations, the TXmay determine whether to operate on, search for, and/or probe aparticular channel based on the likelihood and/or probability of thechannel being a non-overlapping channel.

In some configurations, the data packet may include various portionshaving relatively different characteristics. For instance, a firstportion of the data packet may include a field that is common, shared,and/or otherwise available/provided to every user, receiver,intended/destined recipient, and/or destination of the data packet. Insome configurations, the field that is common, shared, and/or otherwiseavailable/provided to every user, receiver, intended/destined recipient,and/or destination of the data packet may contain an allocation ofresources (e.g., resource units) for each of the user, receiver,intended/destined recipient, and/or destination of the data packet. Asecond portion of the data packet may include a plurality ofuser-specific information that do not belong to the field that iscommon, shared, and/or otherwise available/provided to every user,receiver, intended/destined recipient, and/or destination of the datapacket. There may exist a bit-level separation between the first portionand the second portion. In some configurations, the first and secondportions may be located in a single one of the fields described above(e.g., fields). In some configurations, the first and second portionsmay be located in a plurality of the fields described above (e.g.,fields). In some configurations, the TX may generate and/or transmit adata packet including a header or preamble including a field common to aplurality of users and also including a plurality of fields eachcontaining user-, receiver-, recipient-, and/or destination-specificinformation. In such configurations, the RX may receive and/or decode adata packet including a header or preamble including a field common to aplurality of users and also including a plurality of fields eachcontaining user-, receiver-, recipient-, and/or destination-specificinformation. In some configurations, the RX may utilize the field commonto all users, receivers, recipients, and/or destinations to determinewhich of the resources (e.g., resource units) are allocated to it. Insome configurations, the RX may utilize the user-, receiver-,recipient-, and/or destination-specific information to determine atleast one of user-, receiver-, recipient-, and/or destination-specificidentifier, modulation and coding scheme (MCS), number of space-timestreams corresponding to that specific user, receiver, recipient, and/ordestination. In some configurations, the resource unit and/or resourceallocation may include a portion or subset of the full bandwidth that isallocated to that specific user, receiver, recipient, and/ordestination.

In some configurations, the RX(s) may need to determine whether the datapacket is one of various possible types of data packets. For example,the data packet may be a non-legacy data packet. If the data packet isnot a non-legacy data packet, the data packet may be a legacy datapacket. In some configurations, an auto-detection algorithm fordetermining whether a received data packet is a legacy or non-legacydata packet may provide certain enhancements to the overall system. Anauto-detection algorithm for determining whether a received data packetis a legacy or non-legacy data packet may involve performing acomparison or evaluation between/among various portions, bits, segments,or other subparts of the overall data packet. For instance, the RX mayreceive a data packet that includes a header/preamble, determine whetherany portion of the header/preamble of the data packet is repeated atleast once, and determine whether the data packet is a legacy ornon-legacy data packet based on the determination that that particularportion of the header/preamble portion of the data packet is repeated atleast once. For example, if that particular portion is not repeated atleast once, then the RX may determine that the data packet is a legacydata packet. As another example, if that particular portion is repeatedat least once, then the RX may determine that the data packet is not alegacy data packet. This particular portion may be any portion or anentirety of any one or more of the fields described in greater detailabove without deviating from the scope of the present disclosure.

In some configurations, the repetition of a particular portion of thedata packet may trigger the RX to change its mode of operation from onemode to another mode. For example, the RX may be in an outdoor area andthus may benefit from changing its settings in order to operate in anoutdoor or extended mode of operation. Accordingly, the TX may generateand/or transmit the data packet such that a particular portion isrepeated at least once. The RX may receive and/or decode the data packet(including that particular portion) and, in response to detecting the(at least once) repetition of that particular portion, determine tochange its mode of operation from its current mode of operation toanother mode of operation. A non-limiting example involves changing themode of operations to an outdoor or extended mode of operation, but themode of operation can be changed to any other mode of operation (otherthan the current mode of operation) without deviating from the scope ofthe present disclosure. This particular portion may be any portion or anentirety of any one or more of the fields described in greater detailabove without deviating from the scope of the present disclosure.

In some circumstances, one of the apparatuses (e.g., RXs/STAs) maytransmit a message to another apparatus (e.g., TX/AP) to indicatewhether a particular signal previously transmitted by that apparatus(e.g., TX/AP) was successfully received and/or decoded (e.g., at theRX). As an example, when that particular signal was successfullyreceived and/or decoded, the RX/STA may transmit an acknowledgementmessage (ACK). As another example, when that particular signal was notsuccessfully received and/or decoded, the RX/STA may transmit a negativeacknowledgement message (NACK). A message may refer to a frame, packet,data packet, any sequence of bits/bytes/octets, and/or other suitableterms. In some configurations, such a message may be a blockacknowledgement message (BA). While an ACK/NACK may indicate whether asingle frame/packet was successfully received and/or decoded, a BA maybe a message that indicates whether a plurality of frames/packets (e.g.,MPDUs) were successfully received and/or decoded. In systems, such amessage (e.g., ACK/NACK/BA) may be transmitted by one apparatus (e.g.,RX/STA) at a time. In other words, RX₁ may transmit such a message(e.g., ACK/NACK/BA) at Time₁, and RX₂ may transmit another such message(e.g., ACK/NACK/BA) at Time₂.

However, when a relatively high number of such apparatuses (e.g.,RXs/STAs) exist in a BSS or communication range associated with orcorresponding to the other apparatus (e.g., TX/AP) to which that message(e.g., ACK/NACK/BA) is being sent, the amount of time consumed/utilizedfor communicating such messages (e.g., ACK/NACK/BA) by all of thoseapparatuses (e.g., RXs/STAs) may be considerable. In someconfigurations, multiple apparatuses (e.g., RXs/STAs) may transmit sucha message (e.g., ACK/NACK/BA) at the same (or similar or substantiallysimilar/same) time. For example, in some configurations, RX₁ maytransmit such a message (e.g., ACK/NACK/BA) at Time₁, and RX₂ maytransmit such a message also at (or approximately at) Time₁. Suchaspects may sometimes be referred to as a multi-user (MU) transmission.Such aspects may sometimes be referred to an UL MU transmission. In someconfigurations, such messages may be multiplexed. Multiplexing may referto a method, process, and/or algorithm of combining multiple (e.g., aplurality of) signals/messages/packets/frames (e.g., ACK/NACK/BA) into asingle signal/message/packet/frame. Multiplexing may refer to or includespace-division multiplexing, frequency-division multiplexing,time-division multiplexing, polarization-division multiplexing,code-division multiplexing, orbital angular momentum multiplexing,and/or various other suitable types/forms of multiplexing.

As an example, the message (e.g., ACK/NACK/BA) from RX₁ may bemultiplexed with the message (e.g., ACK/NACK/BA) from RX₂. In otherwords, the ACK/NACK/BA can be a multiplexed UL MU transmission. Prior tosuch multiplexing, in some configurations, one apparatus (e.g., TX/AP)may transmit to one or more other apparatuses (e.g., RX₁/STA₁, RX₂/STA₂,etc.) a request message to solicit an acknowledgement message (e.g.,ACK/NACK/BA) from multiple (e.g., a plurality of) other apparatuses(e.g., RX₁/STA₁, RX₂/STA₂, etc.). Such a request message may sometimesbe referred to as an ACK request, a NACK request, a BA request, and/orany other suitable term. Such a request message may also be referred toas a multi-user message (e.g., a multi-user ACK request, a multi-userNACK request, a multi-user BA request). Such a request message may besent to multiple (e.g., a plurality of) such apparatuses (e.g.,RX₁/STA₁, RX₂/STA₂, etc.). In some circumstances, such a request messagemay be sent to multiple (e.g., a plurality of) such apparatuses (e.g.,RX₁/STA₁, RX₂/STA₂, etc.) at the same (or substantially similar) time.As an example, an apparatus (e.g., TX/AP) may transmit a request message(e.g., a MU ACK request, a MU NACK request, a MU BA request) to solicita request message (e.g., ACK/NACK/BA) from multiple (e.g., a pluralityof) other apparatuses (e.g., RX₁/STA₁, RX₂/STA₂, etc.) in an UL MUtransmission.

In some configurations, an apparatus (e.g., TX/AP) may transmit amulti-user BA request configured to solicit an ACK/NACK/BA to betransmitted from a plurality of receivers (e.g., RX₁/STA₁, RX₂/STA₂,etc.) of the multi-user BA request at the same time. In someconfigurations, an apparatus (e.g., RX/STA) may receive a multi-user BArequest configured to request an ACK/NACK/BA (e.g., from a plurality ofrecipients). In some configurations, the multi-user BA request may beincluded in an ULTR. In some configurations, the multi-user BA requestmay be included in the data packet (PPDU). The multi-user BA request maybe configured to solicit an ACK/NACK/BA to be transmitted by a pluralityof receivers (e.g., RX₁/STA₁, RX₂/STA₂, etc.) of the multi-user BArequest at the same time. In some configurations, the BA request mayinclude certain data/information (e.g., a receiver identifier, a stationidentifier, an associated identifier, a station/receiver associatedidentifier, BA request control, BA request information) associated withand/or corresponding to each apparatus (e.g., RX/STA). The apparatus(e.g., STA) may also transmit an ACK/NACK/BA when certaindata/information (e.g., a receiver identifier, a station identifier, anassociated identifier, a station/receiver associated identifier, BArequest control, BA request information) included in the multi-user BArequest corresponds to data assigned/associated/stored in the apparatus(e.g. STA).

Information included in frames/packets communicated from one apparatusto another apparatus may be associated with one or more accesscategories, stream identifiers (IDs), traffic categories, and/or trafficIDs. Some systems may only be able to communicate packets/framesassociated with a single access category, stream identifier (ID),traffic category, and/or traffic ID at a single point in time. In otherwords, such systems may transmit a first frame/packet associated with afirst access category, first stream identifier (ID), first trafficcategory, and/or first traffic ID at Time₁, and may have to wait until anext transmission time (e.g., TXOP) to transmit second frame/packetassociated with a second access category, second stream identifier (ID),second traffic category, and/or second traffic ID (which is differentfrom the first stream identifier (ID), the first traffic category,and/or the first traffic ID, respectively, as transmitted at Time₁).

However, enabling transmission of data associated with multiple (e.g., aplurality of different) access categories, stream identifiers (IDs),traffic categories, and/or traffic IDs in a singletransmission/frame/packet may contribute to increased efficiency and/orthroughput. In some configurations, a frame/packet may be a MAC servicedata unit (MSDU), a physical layer service data unit (PSDU), physicallayer convergence protocol (PLCP) protocol data unit (PPDU), and/orvarious other types of frames/packets. In some configurations,data/frames/packets associated with and/or corresponding to multiple(e.g., two or more different) (e.g., a plurality of) access categories,stream identifiers (IDs), traffic categories, and/or traffic IDs may beincluded in a single MSDU/PSDU/PPDU and/or a single ACK/NACK/BAcommunicated between the TX/AP and one or more RXs/STAs during DL and/orUL communication. The frame/packet may be an aggregated frame/packet.For instance, the frame/packet may be an aggregated MSDU, an aggregatedPSDU, an aggregated PPDU, and/or an aggregated other type offrame/packet.

As an example, a TX/AP may transmit a frame/packet comprising a first(data) portion associated with and/or corresponding to a first accesscategory, first stream identifier (ID), first traffic category, and/orfirst traffic ID and further comprising a second (data) portionassociated with and/or corresponding to a second access category, secondstream identifier (ID), second traffic category, and/or second trafficID (which is different from the first stream identifier (ID), the firsttraffic category, and/or the first traffic ID, respectively). In otherwords, the TX/AP may transmit a first frame/packet associated with afirst access category, first stream identifier (ID), first trafficcategory, and/or first traffic ID at Time₁ and (concurrently, in thesame transmission, in the same transmission time interval, in the sameTXOP, and/or in the same frame/packet) also transmit a secondframe/packet associated with a second access category, second streamidentifier (ID), second traffic category, and/or second traffic ID(which is different from the first stream identifier (ID), the firsttraffic category, and/or the first traffic ID).

As mentioned above, a frame/packet may sometimes be referred to as aPPDU. Each PPDU may include an allocation and/or a portion for a payloadof the frame/packet/PPDU. Such an allocation and/or portion (e.g.,payload) may include data sometimes referred to as the MSDU/MPDU.However, the size/duration of the MSDU/MPDU can vary based on manyfactors (e.g., MCS, bandwidth, etc.). In some circumstances, theMSDU/MPDU may be too large/long/big to even fit in and/or beaccommodated by the aforementioned allocation/portion/payload of thePPDU. In some circumstances, the allocation/portion/payload mayaccommodate at least one MSDU/MPDU, but the allocation/portion/payloadmay not accommodate a non-integer number of MSDUs/MPDUs. In suchcircumstances, padding may be added/included to fill the unused portionof the allocation/portion/payload of the PPDU. However, in theaforementioned circumstances, a fragment of the MSDU/MPDU may fit and/orbe accommodated in the allocation/portion/payload of the PPDU, therebypossibly improving the efficiency and throughput of the overall system.

In some configurations, the network/system/device/apparatus/apparatusesmay enable/allow/support/provide/accommodate fragments/fragmentation ofan MSDU/MPDU. For example, an apparatus (e.g., TX/AP) may determine alength/duration/size of a single MSDU/MPDU for transmission in a PPDU.Based on the determined length/duration/size of the single MSDU/MPDU,the apparatus (e.g., TX/AP) may determine how many MSDUs/MPDUs can beincluded in the PPDU. The apparatus (e.g., TX/AP) may determine toinclude a fragment of an MSDU/MPDU when a number of MSDUs/MPDUs that canbe included in the PPDU is a non-integer number. In some configurations,the apparatus (e.g., TX/AP) may determine that a length/duration/size ofa single MSDU/MPDU for transmission in a PPDU is greater than anallocated portion/duration/size in the PPDU when thelength/duration/size of the single MSDU/MPDU for transmission in a PPDUis greater than an allocated portion/duration/size in the PPDU. In someconfigurations, the apparatus (e.g., TX/AP) may determine alength/duration/size of a portion of a PPDU allocated for an MSDU/MPDU,and the apparatus (e.g., TX/AP) may determine to include a fragment ofthe MSDU/MPDU in the PPDU for transmission when the determinedlength/duration/size of the portion of the PPDU allocated for theMSDU/MPDU is less a length/duration/size of at least one entireMSDU/MPDU. In one or more of the aforementioned configurations, theapparatus (e.g., TX/AP) may transmit the PPDU including the fragment ofthe MSDU/MPDU.

In some configurations, an apparatus (e.g., RX/STA) may receive a PPDUthat includes a fragment of an MSDU/MPDU, and the fragment of theMSDU/MPDU includes less than an entirety of a complete MSDU/MPDU. Insome configurations, the determining the length/duration/size of thesingle MSDU/MPDU for transmission in the PPDU is based on at least oneof a bandwidth, MCS, and/or various other factors. The MSDU/MPDU can befragmented dynamically based on various factors, such as a remainingportion of the PPDU allocated for one or more MSDUs/MPDUs, asize/length/duration of padding for the remaining portion of the PPDUallocated for one or more MSDUs/MPDUs, and/or various other suitablefactors.

Sounding protocols may sometimes involve an RX/STA transmitting feedbackframes (e.g., a beamforming frame) one RX/STA at a time. However, in anenvironment with many RXs/STAs, this may cause relatively lengthy delaysfor the TX/AP to receive all of the feedback frames (e.g., beamformingframes) it needs/wants prior to performing a DL transmission to thoseRXs/STAs.

In some configurations, an apparatus (e.g., TX/AP) may transmit an ULTRand, in response to transmitting the ULTR, receive a feedback frame(e.g., a feedback report, a beamforming frame, etc.) from a plurality ofother apparatuses (e.g., RXs/STAs) at a same time. In someconfigurations, an apparatus (e.g., RX/STA) may receive an ULTR and, inresponse to receiving the ULTR, transmit a feedback frame (e.g., afeedback report, a beamforming frame, etc.) at a same time as atransmission of a feedback frame (e.g., a feedback report, a beamformingframe, etc.) by another apparatus (e.g., RX/STA). In someconfigurations, an apparatus (e.g., TX/AP) may, prior to transmitting anULTR, transmit a null data packet announcement frame and transmit a nulldata packet after transmitting the null data packet announcement frame.In some configurations, an apparatus (e.g., RX/STA) may, prior toreceiving an ULTR, receive a null data packet announcement frame andreceive a null data packet after receiving the null data packetannouncement frame.

In some configurations, an apparatus (e.g., STA) maydetermine/read/ascertain a total number of space-time streams (STSs)included in the data packet/frame/etc. using/based on avalue/field/information included in a portion (header) of the datapacket/frame/etc. In some configurations, the apparatus (e.g., STA) maydetermine/read/ascertain a total number of a plurality ofusers/destinations/STAs to which a data packet/frame/etc. isdestined/intended using/based on information included in the datapacket/frame/etc. In some configurations, the apparatus (e.g., STA) mayutilize an identifier/value/field/information included in the frame/datapacket/etc. to select a subset of values from a set of values thatindicate/identify a number of space-time streams destined to at leastone of the plurality of users/destinations/STAs to which the datapacket/frame/etc. is destined/intended. In some configurations, at leastone of the values in the selected subset of values (indicating thenumber of space-time streams destined to at least one of theusers/destinations/STAs) varies/ranges/depends upon various factors. Insome configurations, the apparatus (e.g., STA) maydetermine/calculate/compute an (exact) value for the at least one of thevalues in the selected subset of values that varies/ranges byconsidering a total number of STSs included in the datapacket/frame/etc. In some configurations, the apparatus (e.g., STA) maydetermine/calculate/compute an (exact) value for the at least one of thevalues in the selected subset of values that varies/ranges bydeducting/subtracting some or all other values in the selected subset ofvalues from the total number of STSs included in the datapacket/frame/etc.

In some configurations, the apparatus (e.g., STA) maydetermine/calculate/compute an (exact) value for the at least one of thevalues in the selected subset of values that varies/ranges byeliminating one or more possible values if an addition of those one ormore possible values to the other subset of values generates a sums thatexceeds the total number of STSs included in the data packet/frame/etc.In some configurations, the apparatus (e.g., STA) may determine a valueof a user position assigned/allocated to the STA. In someconfigurations, the apparatus (e.g., STA) may select which of (e.g.,which may be different from just how many) of the streams of theplurality of STSs included in the data packet/frame/etc. is/are destinedto/intended for the apparatus (e.g., STA) by considering a number ofSTSs allocated/assigned to other apparatuses (e.g., STAs) that areassigned/allocated user position values different from (e.g., lower invalue than) the value of the user position assigned/allocated to theapparatus (e.g., STA). In some configurations, a number of STSsintended/destined for/to a first user/destination/STA may be greaterthan or equal to (e.g., never exceed) a number of STSs intended/destinedfor/to a second user/destination/STA. Any number ofspatially-multiplexed users in a DL or UL MU-MIMO transmission may beimplemented. Any number of STS values for each user in a MU-MIMO RU maybe implemented. In many other configurations, another apparatus (e.g.,AP, another STA) may perform transmitter-side processes that relateto/pertain to the receiver-side processes described above with referenceto a STA. In some configurations, an apparatus (e.g., STA) having/with apending UL data, after receiving a MU DL transmission, may set a bit inits UL MU response frame (e.g., an acknowledgement of some sort). Thatbit may be configured to inform the receiving apparatus (e.g., AP,another STA) that the transmitting apparatus (e.g., STA) has a pendingUL data ready for near future transmission.

At block 406, an apparatus may enable aspects related to performingcommunications regarding UL communication(s). In some aspects, at timeT_(iv), an AP may transmit and/or an STA may receive asignal/transmission (e.g., DL transmission(s) 232, 234) configured totrigger simultaneous/concurrent UL transmission(s) (e.g., ULtransmission(s) 262, 264) by a plurality of STAs within a period of timeafter receiving that signal/transmission (e.g., DL transmission(s) 232,234). As indicated above, such a signal/transmission (e.g., DLtransmission(s) 232, 234) is sometimes referred to as an ULTR and/orvarious other suitable terms (as described in greater detail herein)without deviating from the scope of the present disclosure. The timeduration between time T_(iv) and time T_(vii) may be represent theperiod of time between reception, by the STA(s), of the aforementionedDL transmission(s) 232, 234 (e.g., ULTR(s)) and transmission, by theSTA(s), of the simultaneous/concurrent UL transmission(s) 262, 264. Insome aspects, the ULTR (e.g., DL transmission(s) 232, 234) may bedestined/intended for a plurality of STAs. In some aspects, the ULTR(e.g., DL transmission(s) 232, 234) may include information foridentifying the plurality of STAs for the simultaneous/concurrent ULtransmissions (e.g., UL transmission(s) 262, 264). For example, the ULTR(e.g., DL transmission(s) 232, 234) may identify which of the STAswithin the coverage area of the AP are intended to receive the ULTRand/or intended to perform the simultaneous/concurrent ULtransmission(s) 262, 264. In some aspects, the ULTR (e.g., DLtransmission(s) 232, 234) may include an indication indicating whetherto perform carrier sensing prior to initiating an UL transmission (e.g.,UL transmission(s) 262, 264).

In some aspects, the ULTR (e.g., DL transmission(s) 232, 234) includes afirst portion including a field common to the plurality of STAs andindicating a duration of at least a portion of thesimultaneous/concurrent UL transmission(s) (e.g., UL transmission(s)262, 264). In some aspects, the ULTR (e.g., DL transmission(s) 232, 234)includes a second portion including a plurality of user-specific fieldsindicating a description of resource allocation for thesimultaneous/concurrent UL transmission(s) (e.g., UL transmission(s)262, 264) by the plurality of STAs. For example, the ULTR (e.g., DLtransmission(s) 232, 234) may identify, allocate, assign, and/orotherwise specific resource units (RUs) to be used by each the pluralityof STAs that will be performing the simultaneous/concurrent ULtransmission(s) (e.g., UL transmission(s) 262, 264). In some aspects,the ULTR further comprises an indication indicating whether a subsequentULTR is a cascading ULTR. For example, the ULTR (e.g., DLtransmission(s) 232, 234) may include a field, parameter, value, bit,portion and/or other suitable aspect indicating whether the ULTR will befollowed by another, possibly unscheduled, ULTR.

In some aspects, the ULTR (e.g., DL transmission(s) 232, 234) mayinclude information corresponding to a target received signal strength,which may refer to the desired/targeted power of the signal(s) to bereceived by one or more of the antennas of the AP(s) (e.g., thedesired/targeted power of the UL transmission(s) 262, 264). In someaspects, the ULTR (e.g., DL transmission(s) 232, 234) may includeinformation corresponding to a power measurement of the transmittedULTR, wherein the power measurement of the transmitted ULTR may refer tothe power utilized to transmit the ULTR (e.g., DL transmission(s) 232,234) using one or more antennas of the AP(s). In some aspects, based onthe information corresponding to the power measurement of thetransmitted ULTR (as included in the ULTR), an STA (e.g., STA₁ 114, STA₂116) may determine an amount of power loss during the DL transmission ofthe ULTR (e.g., DL transmission(s) 232, 234) from an apparatus (e.g.,AP₁ 112) to the STA (e.g., STA₁ 114, STA₂ 116). For example, the STA(e.g., STA₁ 114, STA₂ 116) may consider the received informationcorresponding to the power measurement of the transmitted ULTR (e.g., DLtransmission(s) 232, 234) in relation to the measured signal strength ofthe received ULTR in order to determine the amount of power loss duringthe DL transmission of the ULTR.

In some aspects, prior to receiving the ULTR (e.g., DL transmission(s)232, 234), an AP may transmit and an STA may receive asignal/transmission indicating a start time associated withcommunication of an ULTR from the AP. Subsequently, the STA may enter alow-power mode until a time corresponding to the start time indicated inthe received signal/transmission. By entering into the low-power mode,the STA can conserve power that might otherwise be expended prior to theapproximate start time of the ULTR communication. In some aspects, theULTR is further configured to assign at least one RU for random access.For example, DL transmission(s) 232, 234 may be configured to assign atleast one RU for random access for UL multiuser transmission(s) (e.g.,UL transmission(s) 262, 264).

In some configurations, the transmission of a data packet (e.g., datapacket) may be from a TX to a plurality of RXs. Such a transmission maysometimes be referred to as a downlink (DL) transmission. In someconfigurations, the transmission of a data packet (e.g., data packet)may be from a plurality of RXs to the TX. Such a transmission may bereferred to as an uplink (UL) transmission (or, alternatively, amulti-user UL transmission). In some configurations, the TX maycoordinate the timing of the UL transmission from the plurality of RXsto the TX. Such a coordination procedure may at least in part includetransmission of an UL transmission request (ULTR) from the TX to one ormore of the plurality of RXs. The ULTR may be referred to by any othersuitable name (e.g., UL request, UL response, trigger/triggeringdata/portion/packet/frame, etc.) without deviating from the scope of thepresent disclosure. In some configurations, the ULTR may be a controlframe (or part of a control frame). In some configurations, the ULTR maybe a management frame (or part of a control frame). In someconfigurations, the ULTR may be a data frame (or part of a data frame).In some configurations, the ULTR may be a unicast frame. In someconfigurations, the ULTR is a multicast frame. In some configurations,the ULTR is transmitted at random times. In some configurations, theULTR is transmitted at a target transmission time. The targettransmission time may be determined based on various factors withoutdeviating from the scope of the present disclosure. For instance, insome configurations, the target transmission time for transmitting theULTR may be associated with and/or corresponding to a target wake time.Generally, the target wake time is a function that permits the TX todefine a specific time or set of times for individual RXs to access atransmission medium. The RX and the TX may exchange information thatincludes an expected activity duration to allow the TX to control theamount of contention and overlap among other/competing RXs. The TX mayprotect the expected duration of activity with various protectionmechanisms. The target wake time may be determined implicitly and/orexplicitly without deviating from the scope of the present disclosure.For example, the target wake time may be broadcasted in a beacon signal.As another example, the target wake time may be negotiated. Even the useof the target wake time may sometimes be negotiated between the TX andone or more RXs. In some configurations, the ULTR is part of a datapacket (e.g., data packet), such as a PPDU. In some configurations, theULTR is separate from the data packet (e.g., data packet), such as aPPDU; rather, the ULTR is either a standalone frame or data packet, orincluded with another data packet. In some configurations, the ULTR is acontrol format that carries information sufficient to identify the RX(s)transmitting the UL data packet (e.g., a multi-user UL PPDU) and/orallocating resources for the UL data packet (e.g., a multi-user ULPPDU). In some configurations, the ULTR is configured to trigger an ULtransmission by each of the RXs, receivers, users, destinations, andintended recipients that receive the ULTR and/or the data packet (whichmay sometimes include the ULTR) within a certain period of time (e.g.,inter-frame spacing (IFS)). In some configurations, the UL transmissionthat follows the ULTR may begin at a time that is indicated in the ULTR.In some configurations, the UL transmission that follows the ULTR mayend/terminate at a time that is indicated in the ULTR. In someconfigurations, the ULTR may indicate the duration of the ULtransmission that follows the ULTR. In some configurations, the ULTR mayinclude various field configured to include various types ofinformation, data, and content without deviating from the scope of thepresent disclosure. For instance, the ULTR may include a first portionincluding a field common to, shared with, and/or otherwiseavailable/provided to a plurality of RXs. The field common to, sharedwith, and/or otherwise available/provided to the plurality of RXs mayinclude various subfields characterizing or defining the format of theinformation included in the ULTR. The field common to, shared with,and/or otherwise available/provided to the plurality of RXs mayadditionally or alternatively include the duration of the UL data packet(e.g., a multi-user UL data packet). The field common to, shared with,and/or otherwise available/provided to the plurality of RXs mayadditionally or alternatively include thegoal/objective/reason/purpose/intent of the UL data packet (e.g., amulti-user UL data packet). The ULTR may also include a second portionincluding a plurality of user-specific fields containing informationthat do not belong to the field that is common, shared, and/or otherwiseavailable/provided to all of the plurality of RXs. In someconfigurations, the plurality of user-specific fields may include anidentifier or identification of the RX(s). In some configurations, theplurality of user-specific fields may include a description of theresource allocation (e.g., resource units) for the UL data packet and/orits corresponding UL transmission. In some configurations, the pluralityof user-specific fields may include information associated with thepower level for the UL transmission of the UL data packet, or any othersuitable/revenant aspect.

As described above, the ULTR may be included as a part of any datapacket. In some configurations, the ULTR may be included as a part ofthe DL data packet (e.g., a multi-user DL data packet). In someconfigurations, the ULTR may be appended to an end portion of one ormore data portions (e.g., Aggregated MAC Protocol Data Unit(s)[A-MPDU(s)]) of one or more portions (e.g., space-time stream(s)) of theDL data packet. In some configurations, the ULTR may be multiplexedacross/over/throughout/onto one or more data portions (e.g., A-MPDU(s))of the DL data packet (e.g., multi-user DL data packet). Suchmultiplexing may occur in the frequency domain and/or the spatialdomain. By including the ULTR as a part of the DL data packet, the ULTRmay not need to be transmitted as a separate frame/packet, therebypossibly reducing the need for certain IFS prior to and/or following theULTR. Also, the ULTR may be able to piggy-back onto the DL data packet(e.g., multi-user DL data packet), thereby possibly reducing the needfor some overhead (e.g., headers, preambles, etc.) that might otherwisebe needed for a separately-transmitted ULTR. Accordingly, the TX maygenerate and/or transmit a DL data packet (e.g., a multi-user DL datapacket) including a data portion (e.g., A-MPDU) and also including atleast one ULTR, and the RX may receive and/or decode the DL data packet(e.g., a multi-user DL data packet) including the data portion (e.g.,A-MPDU) and also including the at least one ULTR. Subsequently, withouttransmitting another (or a separate) ULTR, the RX may generate and/ortransmit the UL data packet (e.g., a multi-user UL data packet), and theTX may receive and/or decode the UL data packet (e.g., a multi-user ULdata packet). In some configurations, the DL data transmission and theUL data transmission may occur during a single transmission opportunity(TXOP). In other words, the DL data packet is generated and/ortransmitted during a TXOP that is the same as the TXOP during which theUL data packet is generated and/or transmitted. In other words, the TXmay generate/transmit a data packet (e.g., PPDU) including one or moredata portions (e.g., A-MPDUs) to a plurality of RXs. In someconfigurations, the data packet includes the ULTR. In someconfigurations, the ULTR may be configured to trigger a simultaneous ULtransmission by the plurality of STAs within a period of time (e.g.,IFS) after receiving the data packet and/or the ULTR in the data packet.As described above, the ULTR may sometimes be a unicast frame. In someconfigurations, the ULTR may be included for each of the one or moredata portions (e.g., A-MPDUs). In some configurations, each of the oneor more data portions (e.g., A-MPDUs) is destined to a different RX (andthus may have a different ULTR). As described above, the ULTR(s) mayprecede a simultaneous, multi-user UL transmission by the plurality ofRXs.

In some configurations, an apparatus (e.g., TX/AP) may transmitinformation/data/bit(s) indicating whether the receive signal (e.g.,beacon) is associated with two or more ULTRs. In some configurations, anapparatus (e.g., TX/AP) may transmit information/data/bit(s) indicatingthat the two or more ULTRs are cascaded (e.g., transmitted in a cascadedsequence/number). In some configurations, an apparatus (e.g., RX/STA)may disregard/refrain from processing/considering any/every ULTRreceived during a time period beginning from receipt of themessage/signal (e.g., beacon) and ending at the time corresponding tothe scheduling information, the start time, and/or the time intervalincluded in the received signal/message (e.g., beacon).

At block 408, an apparatus may enable aspects related to performingoperations related to at least one NAV. In some aspects, in response toreceiving the ULTR (e.g., DL transmission(s) 232, 234), an STA mayconsider a NAV unless the NAV was set by a frame originating from theapparatus from which the ULTR was transmitted. In some aspects, inresponse to receiving the ULTR (e.g., DL transmission(s) 232, 234),if/when the NAV was (previously) set by a frame originating from an AP(e.g., AP₁ 112) from which the ULTR is transmitted, an STA (e.g., STA₁114, STA₂ 116) may transmit a frame, packet, and/or data unit (e.g., ULtransmission(s) 262, 264) without considering the NAV. In some aspects,an STA (e.g., STA₁ 114, STA₂ 116) may refrain from considering a NAVwhen the NAV was most recently set by an apparatus (e.g., AP₁ 112) thattransmitted the ULTR (e.g., DL transmission(s) 232, 234). For example,referring to FIG. 2, in response to receiving an ULTR (e.g., DLtransmission(s) 232, 234) from AP₁ 112, STA₁ 114 may consider a NAVunless the NAV was most recently set by a frame originating from AP₁112. In some aspects, an STA (e.g., STA₁ 114) may refrain fromconsidering a NAV when an identifier of the apparatus that most recentlyset the NAV (e.g., of STA₁ 114) is the same as an identifier of theapparatus (e.g., AP₁ 112, STA₂ 116) that transmitted the ULTR (e.g., DLtransmission(s) 232, 234). If such an apparatus (e.g., AP₁ 112, STA₂116) had most recently set the NAV of STA₁ 114, then the NAV (e.g., ofSTA₁ 114) may already be configured with parameters and settings thatare relatively less likely to result in interfering communications.Accordingly, refraining from considering the NAV in such circumstancescan conserve time, power, and computational resources.

In some aspects, an STA (e.g., STA₁ 114) may receive a frame (e.g.,included in a transmission 130) from another STA (e.g., STA₂ 116) anduse that frame to set a NAV. In some aspects, the STA (e.g., STA₁ 114)may refrain from considering the NAV of the STA (e.g., STA₁ 114) inresponse to receiving the ULTR (e.g., DL transmission(s) 232, 234 fromAP₁ 112) when an identifier (e.g., a BSS identifier (BSSID), amedium/media access control (MAC) address, etc.) of the BSS with whichthe STA (e.g., STA₁ 114) is associated corresponds to the BSSID of theBSS with which the other STA (e.g., STA₂ 116) is associated. In someaspects, the STA (e.g., STA₁ 114) may refrain from considering a NAV ofthe STA (e.g., STA₁ 114) in response to receiving the ULTR (e.g., DLtransmission(s) 232, 234 from AP₁ 112) when the STA (e.g., STA₁ 114) isin the same BSS as the other STA (e.g., STA₂ 116). When the BSSIDs ofthe STAs are associated and/or when the STAs are in the same BSS, thecommunications of the STAs (STA₁ 114, STA₂ 116) may be centrally managedand/or the likelihood of interference may be relatively low.Accordingly, refraining from considering a NAV in such circumstances canconserve time, power, and computational resources.

In some aspects, in response to receiving the ULTR (e.g., DLtransmission(s) 232, 234), if/when the UL response (e.g., ULtransmission(s) 262, 264) to the ULTR comprises an acknowledgementmessage having less than a threshold duration, an STA (e.g., STA₁ 114,STA₂ 116) may transmit a frame (e.g., UL transmission(s) 262, 264)without considering a NAV. For example, referring to FIG. 2, in responseto receiving a DL transmission 232 (e.g., ULTR) at time T_(iv), the STA(e.g., STA₁ 114), at time T_(v), may refrain from considering a NAV whenthe UL transmission 262, at time T_(vii), includes an acknowledgementmessage having a duration less than a threshold value. For relativelyshort transmissions that communicate acknowledgement information, thetime, power, and computational resources utilized for considering theNAV (e.g., of STA₁ 114) may not be warranted.

In some aspects, an STA may determine whether to update a NAV by usingvarying detection thresholds based on whether a received ULTR, signal,frame and/or data unit is communicated from a same BSS. In some aspects,an STA (e.g., STA₁ 114) may refrain from updating one or more parametersof the NAV if (i) a received ULTR, signal, frame, and/or data unit istransmitted from an apparatus (e.g., AP₂ 142, STA₃ 144, STA₅ 146)associated with a BSS different from a BSS with which the STA (e.g.,STA₁ 114) is associated and/or (ii) a strength of the received ULTR,signal, frame, and/or data unit is less than a first detection thresholdvalue. The first detection threshold value may be greater than a seconddetection threshold value used if the received ULTR, signal, frame,and/or data unit is not transmitted by the apparatus (e.g., AP₂ 142,STA₃ 144, STA₅ 146) associated with the BSS that is different from theBSS with which the STA (e.g., STA₁ 114) is associated (e.g., if thereceived ULTR, signal, frame, and/or data unit is transmitted by anapparatus (e.g., AP₁ 112, STA₂ 116, STA₄ 118) associated with the sameBSS as the STA (e.g., STA₁ 114)). In such aspects, a relatively higherdetection threshold is used when the received ULTR, signal, frame,and/or data unit is transmitted from an apparatus in a different BSS,and a relatively lower detection threshold is used when the receivedULTR, signal, frame, and/or data unit is transmitted from an apparatusin the same BSS. By doing so, communications between apparatuses in thesame BSS have a relatively higher likelihood of updating a NAV, andcommunications between apparatuses in different BSSs have a relativelylower likelihood of updating a NAV.

In some aspects, an STA (e.g., STA₁ 114) may receive a frame from anapparatus (e.g., another STA or an AP), and the frame may includeinformation indicating a duration of time used for updating a NAV ofthat STA (e.g., STA₁ 114). Depending on a difference between thereceived information indicating the duration of time used for updatingthe NAV and an existing duration of time of the NAV, the STA (e.g., STA₁114) may override the existing duration of time of the NAV with thereceived information indicating the duration of time used for updatingthe NAV. The aforementioned difference may be (i) a positive value whenthe duration indicated in the received frame is greater than an existingduration, or (ii) a negative value when the duration indicated in thereceived frame is lesser than the existing duration. When the differenceis a positive value, the STA (e.g., STA₁ 114) may override the existingduration with the duration indicated in the received frame.

In some aspects, an STA (e.g., STA₁ 114) may have more than just oneNAV. In some aspects, an STA (e.g., STA₁ 114) may maintain a pluralityof NAVs, each configured for a particular purpose. In some aspects, anSTA (STA₁ 114) may maintain a plurality of NAVs configured to regulatewhether the STA accesses a wireless medium during a period of time. Theplurality of NAVs may include a first NAV adapted for frames originatingfrom an apparatus (e.g., AP₁ 112, STA₂ 116, STA₄ 118) in a BSS withwhich the STA (e.g., STA₁ 114) is associated, and a second NAV adaptedfor frames originating from an apparatus (e.g., AP₂ 142, STA₅ 146, STA₃144) in a BSS with which the STA (e.g., STA₁ 114) is not associated. Byusing a plurality of NAVs, the STA (e.g., STA₁ 114) can track the timedurations and resources being utilized by not only apparatuses in itscurrent BSS but also time durations and resources being utilized byother apparatuses in one or more overlapping BSSs, thereby enabling theSTA (e.g., STA₁ 114) to better manage potential interference,contention, and/or channel access.

In some aspects, an STA may update each of at least two of the pluralityof NAVs based on various criteria without necessarily deviating from thescope of the present disclosure. In some aspects, an STA (e.g., STA₁114) may receive a frame from an apparatus (e.g., another STA or an AP),and the frame may be configured to update one of a plurality of NAVs ofthe STA. If a BSSID of the BSS with which the STA (e.g., STA₁ 114) isassociated corresponds to a BSSID of a BSS with which the apparatus(e.g., STA₂ 116, AP₁ 112, STA₄ 118) is associated, then an STA (e.g.,STA₁ 114) may update a first NAV (of a plurality of NAVs), wherein thefirst NAV is configured for frames communicated within a BSS with whichthe STA (e.g., STA₁ 114) is associated. If the BSSID of the BSS withwhich the STA (e.g., STA₁ 114) is associated does not corresponds to aBSSID of the BSS with which the apparatus (e.g., AP₂ 142, STA₃ 144, STA₅146) is associated, then an STA (e.g., STA₁ 114) may update a second NAV(of a plurality of NAVs), wherein the second NAV is configured forframes communicated outside of the BSS with which the STA (e.g., STA₁114) is associated.

In some aspects, an STA (e.g., STA₁ 114, STA₂ 116) may determine whetherto perform carrier sensing prior to initiating an UL transmission (e.g.,UL transmission(s) 262, 264) in response to receiving the ULTR (e.g., DLtransmission(s) 232, 234). Carrier sensing may include signal detectionand/or NAV(s) evaluation. Carrier sensing may occur during a time periodthat begins at/after receiving the ULTR (e.g., at/after time T_(iv)) andends at/before transmission of the UL transmission(s) (e.g., at/beforetime T_(vii)). In some aspects, determining whether to perform carriersensing depends on whether the ULTR includes information indicatingwhether to perform the carrier sensing prior to the initiating the ULtransmission in response to receiving the ULTR.

As described above, in some aspects, the ULTR (e.g., DL transmission(s)232, 234) may include an indication indicating whether an STA (e.g.,STA₁ 114, STA₂ 116) is to perform carrier sensing prior to initiating anUL transmission (e.g., UL transmission(s) 262, 264). When/If theindication in the ULTR indicates no requirement to perform carriersensing prior to the UL transmission in response to the ULTR, then theSTA may refrain from performing carrier sensing (for at least asubchannel allocated to the UL transmission). When/If the indication inthe ULTR indicates a requirement to perform carrier sensing prior to theUL transmission in response to the ULTR, then the STA may performcarrier sensing (for at least the subchannel allocated to the ULtransmission).

In some systems, the UL transmission from the RX/STA is initiated by theTX/AP (e.g., rather than the RX/STA). As a result, when the TX/AP sendsthe ULTR, the RX/STA may intend/wish to immediately begin transmissionof an UL transmission. That is, in some systems, the RX/STA may notalways necessarily consider the duration of other transmissions on aparticular channel (e.g., as indicated by the navigation allocationvector) before that immediate UL transmission and, thus, may initiate anUL transmission without considering other protected transmissions onthat particular channel, thereby likely disrupting those othertransmissions and/or possibly colliding with and thus failing with itsown UL transmission. In some configurations, an ULTR may poll the RX/STAfor UL multi-user transmissions. An RX/STA that is polled from an ULTRfor UL multi-user transmissions considers the navigation allocationvector to determine whether to respond to the ULTR. In someconfigurations, the RX/STA may refrain from responding to the poll ifthe navigation allocation vector was set by a frame/packet originatingfrom the TX/AP that sent/transmitted the ULTR. In some configurations,the RX/STA may refrain from responding to the poll if the response tothe ULTR includes an ACK/NACK/BA and the duration of the UL multi-usertransmission is less than a threshold duration.

In some configurations, an apparatus (e.g., RX/STA) may, in response toreceiving an ULTR, consider the navigation allocation vector and/or aduration (of other transmissions) indicated in the navigation allocationvector to determine when/whether to respond to the ULTR. In someconfigurations, such an apparatus (e.g., RX/STA) may refrain fromresponding to an ULTR until after considering the navigation allocationvector and/or a duration (of other transmissions) indicated in thenavigation allocation vector. In some configurations, such an apparatus(e.g., RX/STA) may, in response to receiving an ULTR, transmit aframe/packet without considering the navigation allocation vector and/ora duration (of other transmissions) indicated in the navigationallocation vector when the navigation allocation vector and/or theduration (of other transmissions) indicated in the navigation allocationvector was/is set by a frame/packet/data originating from an apparatus(e.g., TX/AP) from which the ULTR was sent/transmitted. In someconfigurations, such an apparatus (e.g., RX/STA) may, in response toreceiving an ULTR, transmit a frame without considering the navigationallocation vector and/or a duration (of other transmissions) indicatedin the navigation allocation vector when a response to the ULTRcomprises an ACK/NACK/BA and/or a duration of the UL multi-usertransmission is below a threshold value/duration/time/amount.

In some systems, an apparatus (e.g., TX/AP) may send a messageconfigured to and/or comprising information for early termination of atransmission interval and/or TXOP. This message may sometimes bereferred to as a contention free end message/signal and/or any othersuitable message/signal. In some circumstances, an apparatus (e.g.,RX/STA) may be within the communication range of two (or more) otherapparatuses (e.g., TXs/APs). Either (or both) of those apparatuses(e.g., TXs/APs) may send a ULTR. In some configurations, the ULTR mayinclude information for setting a duration of time to protect acommunication channel by preventing/inhibiting other communications forthat duration of time on that communication channel. For example, theULTR may include information for and/or may be configured to set one ormore parameters/settings of a network allocation vector. Also, either(or both) of those apparatuses (e.g., TXs/APs) may send theaforementioned message (e.g., the contention free message/signal) forearly termination of the transmission interval and/or TXOP. Forinstance, if an RX/STA receives such a message from a TX/AP before theend of the transmission interval and/or TXOP that is protected by thenetwork allocation vector as set by another TX/AP, then that RX/STAwould be free to perform transmissions earlier than it should (based onthe settings/parameters set for the network allocation vector), therebyincreasing the likelihood of collisions with transmissions with otherRXs/STAs and/or other TXs/APs.

In some configurations, when an apparatus (e.g., RX/STA) receives aparticular message/signal (e.g., contention free end message/signal) anoverlapping BSS apparatus (e.g., AP/TX), that apparatus (e.g., RX/STA)will not adjust, change, reset, modify, and/or adjust one or moreparameters/settings corresponding to a preceding/most-recent/lastnetwork allocation vector update, which may have been caused by anapparatus (e.g., AP/TX) with which it was assigned/associated (e.g., aninter-BSS AP/TX/apparatus). In some configurations, an apparatus (e.g.,RX/STA) may receive an ULTR from a first other apparatus (e.g., firstTX/AP), wherein the ULTR may be configured to set and/or comprisesinformation for setting one or more parameters/settings of the networkallocation vector. In some configurations, an apparatus (e.g., RX/STA)may receive a message (e.g., contention free end message/signal)configured to and/or comprising information for ending a transmissioninterval and/or transmission opportunity. In some configurations, anapparatus (e.g., RX/STA) may determine whether the message is receivedfrom a second other apparatus (e.g., second TX/AP) is different from thefirst other apparatus (e.g., first TX/AP). In some configurations, anapparatus (e.g., RX/STA) may, if/when the second other apparatus (e.g.,other TX/AP) is the same as the first other apparatus (e.g., firstTX/AP), modify/adjust/change/update/reset the one or more parameters orsettings of the network allocation vector (e.g., based on a time atwhich the aforementioned message is received) (e.g., based oninformation included in the message). In some configurations, anapparatus (e.g., RX/STA) may, if/when the second other apparatus (e.g.,second TX/AP) is different from the first other apparatus (e.g., firstTX/AP), modify/adjust/change/update/reset the one or more parameters orsettings of the network allocation vector (e.g., based on a time atwhich the message is received) (e.g., based on information included inthe message).

In some circumstances, when an apparatus (e.g., RX/STA) receives aparticular PPDU with/at a power, signal strength, and/or received signalstrength indicator (RSSI) below an a particular threshold level, thatapparatus (e.g., RX/STA) not update its network allocation vector. Insome configurations, an apparatus (e.g., RX/STA) may determine the basicservice set to which that apparatus (e.g., RX/STA) isassigned/associated. In some configurations, the apparatus (e.g.,RX/STA) may determine whether a received signal (e.g., PPDU) originatesfrom and/or is transmitted by an apparatus (e.g., TX/AP)assigned/associated with another basic service set (e.g., an overlappingbasic service set) (e.g., a basic service set that is different from thebasic service set to which the apparatus (e.g., RX/STA) isassigned/associated. In some configurations, the apparatus (e.g.,RX/STA) may determine a signal strength (e.g., RSSI) of the receivedsignal. In some configurations, the apparatus (e.g., RX/STA) may, if thereceived signal originates from/is transmitted by an apparatus (e.g.,TX/AP) assigned/associated with another basic service set (e.g.,overlapping basis service set) and the signal strength is less than afirst threshold value/amount (e.g., a firstpredetermined/dynamically-adjusted/fixed/stored threshold value/amount)(e.g., a first preamble detect threshold level/amount) associated withsignals originating from and/or transmitted by apparatuses (e.g.,TXs/APs) assigned/associated with the another basic service set,disregard/ignore/refrain from processing the received signal and/orrefrain from updating/resetting/adjusting/modifying/changing one or moreparameters/settings of the network allocation vector. In someconfigurations, the apparatus (e.g., RX/STA) may, if the received signaloriginates from and/or is not transmitted by the apparatus (e.g., TX/AP)assigned/associated with another basic service set (e.g., an overlappingbasic service set) and the signal strength is equal to and/or greaterthan a second threshold value/amount (e.g., a secondpredetermined/dynamically-adjusted/fixed/stored threshold value/amount)(e.g., a second preamble detect threshold level/amount), thenconsider/process the received signal and/orupdate/reset/adjust/modify/change one or more parameters and/or settingsof the network allocation vector, wherein the second threshold has avalue lower than the first threshold.

In some configurations, an apparatus (e.g., RX/STA) may receive a signal(e.g., PPDU) originating from and/or transmitted by an apparatus (e.g.,TX/AP) assigned/associated with a basic service set different from thebasic service set to which the that apparatus (e.g., RX/STA) isassigned/associated. In some configurations, the apparatus (e.g.,RX/STA) may determine whether to consider/process the received signaland/or update/reset/adjust/modify/change one or more parameters/settingsof the network allocation vector based on a signal strength (e.g., RSSI)of the received signal. In some configurations, the apparatus (e.g.,RX/STA) may receive a signal (e.g., PPDU) originating from and/ortransmitted by an apparatus (e.g., TX/AP) assigned/associated with abasic service set different from the basic service set to which the STAis assigned/associated. In some configurations, the apparatus (e.g.,RX/STA) may refrain from considering/processing the received signaland/or updating/resetting/adjusting/modifying/changing one or moreparameters/settings of the network allocation vector when a signalstrength (e.g., RSSI) of the received signal is less than a firstthreshold value/amount (e.g., a firstpredetermined/dynamically-adjusted/fixed/stored threshold value/amount)(e.g., a preamble detect threshold level/amount) that is greater than asecond threshold value/amount (e.g., a secondpredetermined/dynamically-adjusted/fixed/stored threshold value/amount)(e.g., a second preamble detect threshold level/amount) associated withand/or corresponding to signals received from an apparatus (e.g., TX/AP)assigned/associated with the basic service set to which the apparatus(e.g., RX/SAT) is associated/assigned. In some configurations, theapparatus (e.g., RX/STA) may refrain from using the medium forcommunication for a period of time that is at least as long as aduration or length corresponding to the received signal (e.g., PPDU).

In some configurations, an apparatus (e.g., STA) may consider the NAVprior to initiating/performing any transmission. If the NAV has been setsuch that no transmission is allowed at a particular time, then that(e.g., STA) may refrain from transmitting any signals at that time. Forexample, when an apparatus (e.g., STA) receives an ULTR frame, theapparatus (e.g., STA) may consider the NAV to determine whether totransmit an UL signal/transmission. However, in some circumstances, theapparatus (e.g., STA) may not need to always consider the NAV.Considering the NAV settings may cause unnecessary processing time,power consumption, and/or complexity. In some configurations, anapparatus (e.g., STA) that is polled from an ULTR frame for UL MUtransmission may consider the NAV in determining whether to respondunless one or more conditions exists and/or are met. An example of sucha condition may be that the NAV was set by a frame originating from theAP sending the ULTR frame. Another example of such a condition may bethat the response (e.g., to the ULTR) contains an ACK and/or BA and theduration of the UL MU transmission may be below a predeterminedthreshold. Yet another example of such a condition is that the NAV wasset by a frame originating from an intra-BSS STAs.

In some configurations, the apparatus (e.g., STA) may receive a ULTRframe from another apparatus (e.g., AP, another STA). In someconfigurations, the apparatus (e.g., STA) may determine whether the ULTRframe is destined to/intended for the STA. In some configurations, theapparatus (e.g., STA) may determine an identity/identifier/type ofapparatus that transmitted the ULTR frame. In some configurations, theapparatus (e.g., STA) may determine the identify/identifier/type of theapparatus (e.g., AP, another STA) that (most recently) set the NAV ofthe STA. In some configurations, the apparatus (e.g., STA) may comparethe identity/identifier/type of the apparatus (e.g., AP, another STA)that transmitted the ULTR frame with identity/identifier/type of theapparatus (e.g., AP, another STA) that (most recently) set the NAV ofthe STA. In some configurations, the apparatus (e.g., STA) may determinewhether to respond to the ULTR frame by considering whether the NAV ofthe apparatus (e.g., STA) was (most recently) set/adjusted/updated bythe apparatus (e.g., AP, another STA) that transmitted the ULTR frame.In some configurations, the apparatus (e.g., STA) may determine whetherto consider the NAV. In some configurations, the apparatus (e.g., STA)may determine whether to consider the NAV based on the aforementionedcomparison. In some configurations, the apparatus (e.g., STA) mayrefrain from considering the NAV (in determining whether to respond tothe ULTR frame) when the identity/identifier of the apparatus (e.g., AP,another STA) that (most recently) set/adjusted/updated the NAV is thesame as the identity/identifier of the apparatus (e.g., AP, another STA)that transmitted the ULTR frame. In some configurations, the apparatus(e.g., STA) may consider the NAV (in determining whether to respond tothe ULTR frame) when the identity/identifier of the apparatus (e.g., AP,another STA) that (most recently) set/adjusted/updated the NAV isdifferent from the identity/identifier of the apparatus (e.g., AP,another STA) that transmitted the ULTR frame. In some configurations,the apparatus (e.g., STA) may refrain from considering the NAV (indetermining whether to respond to the ULTR frame) when the NAV (e.g., ofthe STA) was (most recently) set/adjusted/updated by the apparatus(e.g., AP, another STA) that transmitted the ULTR frame. In someconfigurations, the apparatus (e.g., STA) may consider the NAV (indetermining whether to respond to the ULTR frame) when the NAV (e.g., ofthe STA) was (most recently) not set/adjusted/updated by the apparatus(e.g., AP, another STA) that transmitted the ULTR frame. The determiningwhether to consider the NAV may be performed while/prior to/afterdetermining whether to respond to the ULTR frame.

In some configurations, a first STA may receive a frame from a secondSTA. In some configurations, the frame is an UL transmission. In someconfigurations, the frame is intended/destined for/to an apparatus(e.g., AP, another STA) other than the first STA. In someconfigurations, the frame is configured to set/update/adjust settings ofthe NAV of the first STA. In some configurations, the frame includesinformation that indicates a duration of a transmission or a TXOP of the(current) frame. In some configurations, the first STA may use the frameand/or information included in the frame to set/adjust/update the NAV ofthe first STA. In some configurations, the first STA may determinewhether the second STA is in a same BSS as the first STA. In someconfigurations, the first STA may determine whether the BSSID of the BSSwith which the first STA is associated is the sameas/matches/corresponds to the BSSID of the BSS with which the second STAis associated. In some configurations, the first STA may compare theBSSID of the BSS with which the first STA is associated with the BSSIDwith which the second STA is associated to determine whether the firstSTA is in a same BSS as the second STA. In some configurations, thefirst STA may receive a ULTR from another apparatus (e.g., AP, anotherSTA) that is different from the first and second STAs. In someconfigurations, the first STA may determine whether to respond to theULTR received from the other apparatus (e.g., AP, another STA) byconsidering whether the NAV of the first STA was (most recently)set/adjusted/updated by the second STA. In some configurations, thefirst STA may refrain from considering the NAV (in determining whetherto respond to the ULTR frame) when the second STA is in a same BSS asthe first STA. In some configurations, the first STA may consider theNAV (in determining whether to respond to the ULTR frame) when thesecond STA is in a different BSS as the first STA. In someconfigurations, the first STA may refrain from considering the NAV (indetermining whether to respond to the ULTR frame) when the BSSID of theBSS with which the first STA is associated is the sameas/matches/corresponds to the BSSID of the BSS with which the second STAis associated. In some configurations, the first STA may consider theNAV (in determining whether to respond to the ULTR frame) when the BSSIDof the BSS with which the first STA is associated is differentfrom/unmatched with/uncorrelated with/does not correspond to the BSSIDof the BSS with which the second STA is associated. In someconfigurations, the first STA may refrain from considering the NAV (indetermining whether to transmit a signal) when the signal/frame/packetis an ACK or BA. In some configurations, the first STA may consider theNAV (in determining whether to transmit a signal/frame/packet) when thesignal is not an ACK or BA.

In some configurations, an apparatus (e.g., STA) may utilize/implement aNAV to regulate whether it accesses a wireless medium during varioustimes. In some circumstances, that apparatus (e.g., STA) may receiveinformation for setting/adjusting/resetting the NAV in framesoriginating from within its BSS (e.g., intra-BSS) (e.g., a BSS withwhich it is not associated) and information forsetting/adjusting/resetting the NAV in frames originating from outsideof its BSS (e.g., inter-BSS) (e.g., a BSS with which it is notassociated). In some circumstances, it may not be ideal to have a singleNAV because at least some of the aforementioned information maybe/become ignored/disregarded/unused. In some configurations, anapparatus (e.g., STA) maintains a plurality (e.g., two or more) NAVs.One NAV may be adapted for intra-BSS frames and another NAV may beadapted for inter-BSS frames. Frames that cannot be conclusivelyclassified/characterized as intra-BSS frames nor inter-BSS frames may bepaired with either of these NAVs.

In some configurations, an apparatus (e.g., STA) may receive a frame(e.g., ULTR frame, MU UL frame, etc.) that is configured toset/updated/adjust a NAV of the apparatus (e.g., STA), and/or includesinformation indicating a setting, duration of time or TXOP that isassociated with/can be used to set/update/adjust a NAV of the apparatus(e.g., STA). In some configurations, the apparatus (e.g., STA) maydetermine whether the received frame originates from another apparatus(e.g., AP, another STA) that is associated with a basic service set(BSS) with which the apparatus (e.g., STA) is associated. In someconfigurations, the apparatus (e.g., STA) may determine whether thatother apparatus (e.g., AP, another STA) is in a same BSS as theapparatus (e.g., STA). In some configurations, the apparatus (e.g., STA)may determine whether an identifier (e.g., BSSID, BSS type, BSScategory, BSS color) of a BSS with which the apparatus (e.g., STA) isassociated is the same as/matches/corresponds to an identifier (e.g.,BSSID, BSS type, BSS category, BSS color) of a BSS with which the otherapparatus (e.g., AP, another STA) is associated. In some configurations,the apparatus (e.g., STA) may compare an identifier (e.g., BSSID, BSStype, BSS category, BSS color) of a BSS with which the apparatus (e.g.,STA) is associated with an identifier (e.g., BSSID, BSS type, BSScategory, BSS color) of a BSS that the other apparatus (e.g., AP,another STA) is associated to determine whether the apparatus (e.g.,STA) is in a same BSS as that of the other apparatus (e.g., AP, anotherSTA). In some configurations, the apparatus (e.g., STA) may, based onsuch a comparison and/or determination, select one of a plurality ofNAVs of the apparatus (e.g., STA) to set/adjust/update (e.g., accordingto the included information described above). In some configurations,the apparatus (e.g., STA) may determine that the BSS with which theother apparatus (e.g., AP, another STA) is associated is not the sameas/does not match/does not correspond/is uncorrelated with the BSS withwhich the apparatus (e.g., STA) is associated when the identifier (e.g.,BSSID, BSS type, BSS category, BSS color) of the BSS with which theapparatus (e.g., STA) is associated is not the same as/does notmatch/does not correspond/is uncorrelated with an identifier (e.g.,BSSID, BSS type, BSS category, BSS color) of a BSS with which the thatother apparatus (e.g., AP, another STA) is associated.

In some configurations, an apparatus (e.g., STA) may determine that theBSS with which the other apparatus (e.g., AP, another STA) is associatedis the same as/matches/does correspond/is correlated with the BSS withwhich the apparatus (e.g., STA) is associated when the identifier (e.g.,BSSID, BSS type, BSS category, BSS color) of the BSS with which theapparatus (e.g., STA) is associated is the same as/does match/doescorrespond/is correlated with an identifier (e.g., BSSID, BSS type, BSScategory, BSS color) of a BSS with which the that other apparatus (e.g.,AP, another STA) is associated. In some configurations, the apparatus(e.g., STA) may designate/characterize/associate the frame as anintra-BSS frame (or a non-intra-BSS frame (e.g., any frame that is notdetermined to be an intra-BSS frame) based on the aforementionedcomparison and/or determination. In some configurations, the apparatus(e.g., STA) may set/update/adjust a first NAV allocated/dedicatedfor/configured for frames communicated inside/within/intra—the BSS withwhich the apparatus (e.g., STA) is associated when the identifier (e.g.,BSSID, BSS type, BSS category, BSS color) of the BSS with which theapparatus (e.g., STA) is associated is the same as/does match/doescorrespond/is correlated with an identifier (e.g., BSSID, BSS type, BSScategory, BSS color) of a BSS with which the that other apparatus (e.g.,AP, another STA) is associated. In some configurations, the apparatus(e.g., STA) may set/update/adjust a second NAV (different from the firstNAV) allocated/dedicated for/configured for all other frames (e.g.,frames communicated outside-of/not-within/inter-the BSS with which theapparatus (e.g., STA) is associated) when the identifier (e.g., BSSID,BSS type, BSS category, BSS color) of the BSS with which the apparatus(e.g., STA) is associated is not the same as/does not match/does notcorrespond to/is uncorrelated with an identifier (e.g., BSSID, BSS type,BSS category, BSS color) of a BSS with which the that other apparatus(e.g., AP, another STA) is associated.

In some configurations, an apparatus (e.g., STA) may determine adifference between a setting, duration of time or TXOP set for the firstNAV and determined a setting, duration of time or TXOP set for thesecond NAV. In some configurations, the apparatus (e.g., STA) maydetermine a difference between a setting, duration of time or TXOP setfor the first NAV and a setting, duration of time or TXOP set for thesecond NAV. In some configurations, the apparatus (e.g., STA) maydetermine whether a difference exists between a setting, duration oftime or TXOP set for the first NAV and a setting, duration of time orTXOP set for the second NAV. In some configurations, the apparatus(e.g., STA) may adjust (e.g., increase/decrease) a setting, duration oftime or TXOP of either the first NAV or the second NAV based on variousfactors. In some configurations, the apparatus (e.g., STA) may overridea setting, duration of time or TXOP set for or associated with the firstNAV with a setting, duration of time or TXOP set for or associated withthe second NAV. In some configurations, the apparatus (e.g., STA) mayadjust (e.g., increase) a setting, duration of time or TXOP associatedwith or set for the first NAV by/based on a difference between asetting, duration of time, or TXOP associated with or set for the firstNAV and a setting, duration of time, or TXOP associated with or set forthe second NAV. In some configurations, the apparatus (e.g., STA) mayoverride a setting, duration of time or TXOP set for or associated withthe second NAV with a setting, duration of time or TXOP set for orassociated with the first NAV. In some configurations, the apparatus(e.g., STA) may adjust (e.g., increase) a setting, duration of time orTXOP associated with or set for the second NAV by/based on a differencebetween a setting, duration of time, or TXOP associated with or set forthe first NAV and a setting, duration of time, or TXOP associated withor set for the second NAV.

In some configurations, an apparatus (e.g., STA) may receive a frame(e.g., ULTR frame, MU UL frame, etc.) that is configured toset/updated/adjust a NAV of the apparatus (e.g., STA) and/or includesinformation indicating a setting, duration of time or TXOP that isassociated with or used for setting/updating the NAV. In someconfigurations, the apparatus (e.g., STA) may compare a setting,duration of time, TXOP that is associated with or used forsetting/updating the NAV of the apparatus (e.g., STA) with anexisting/current/stored/previously-set setting, duration of time, TXOPof the NAV of the apparatus (e.g., STA). In some configurations, theapparatus (e.g., STA) may compute/calculate a difference between asetting, duration of time, TXOP that is associated with or used forsetting/updating the NAV and an existing/current/stored/previously-setsetting, duration of time, TXOP of the NAV of the apparatus (e.g., STA).If the computed/calculated difference is a positive value, in someconfigurations, the apparatus (e.g., STA) may consider both the receivedsetting, duration of time, TXOP that is associated with or used forsetting/updating the NAV of the apparatus (e.g., STA) and theexisting/current/stored/previously-set setting, duration of time, TXOPof the NAV of the apparatus (e.g., STA). In other words, if thecomputed/calculated difference is a positive value, in someconfigurations, the apparatus (e.g., STA) may override theexisting/current/stored/previously-set setting, duration of time, TXOPof the NAV of the apparatus (e.g., STA) with the received setting,duration of time, TXOP that is associated with or used forsetting/updating the NAV of the apparatus (e.g., STA). On the otherhand, if the computed/calculated difference is not a positive value(e.g., zero or less), in some configurations, the apparatus (e.g., STA)may consider (e.g., only) the existing/current/stored/previously-setsetting, duration of time, TXOP of the NAV of the apparatus (e.g., STA).In other words, if the computed/calculated difference is not a positivevalue (e.g., zero or less), in some configurations, the apparatus (e.g.,STA) may disregard/ignore the received setting, duration of time, TXOPthat is associated with or used for setting/updating the NAV of theapparatus (e.g., STA).

In some configurations, a first apparatus (e.g., first STA) may considera procedure based on received signal information (e.g., received signalstrength indicator(s) (RSSI(s)) of two or more frames in determiningwhether to avoid updating the NAV of the apparatus (e.g., STA). In someconfigurations, the first apparatus (e.g., first STA) may determinewhether to reset/set/adjust/update one or more settings, times,durations of the NAV based on/using/by considering RSSI informationreceived for the first signal transmitted from a second apparatus to athird apparatus and RSSI information received for a second signaltransmitted from the third apparatus to the second apparatus in responseto the first signal. In some configurations, the first apparatus (e.g.,first STA) may refrain from resetting/setting/updating/adjusting one ormore settings of the NAV of/associated with the first apparatus (e.g.,first STA) when the RSSI information for the first signal is equal to orbelow a first threshold value and/or the RSSI information for the secondsignal is equal to or below a second threshold value. In someconfigurations, the first and second threshold values may be equal to,different from, greater than, and/or less than each other. In someconfigurations, the first apparatus (e.g., first STA) may refrain fromresetting/setting/updating/adjusting one or more settings of the NAVof/associated with the first apparatus (e.g., STA) when a differencebetween the RSSI information for/associated with the first signal isequal to, less than and/or greater than the RSSI information for thesecond signal by a certain threshold amount, percentage, standarddeviation, etc.

In some configurations, a first apparatus (e.g., first STA) maydetermine to reset/set/update/adjust one or more settings of the NAVof/associated with the first apparatus (e.g., first STA) when the RSSIinformation for the first signal is equal to or above a first thresholdvalue and/or the RSSI information for the second signal is equal to orabove a second threshold value. The first and second threshold value maybe equal to, different from, greater than, and/or less than each other.In some configurations, the first apparatus (e.g., first STA) mayreset/set/update/adjust one or more settings of the NAV of/associatedwith the first apparatus (e.g., STA) when a difference between the RSSIinformation for the first signal is less than or greater than the RSSIinformation for the second signal by a certain threshold amount,percentage, standard deviation, etc. In some configurations, the firstsignal may be a ULTR frame, a request to send (RTS), and/or any othersuitable (triggering) signal/message and the second signal is a MU ULframe, a clear to send (CTS), and/or any other suitable responsesignal/message (to the triggering signal/message).

At block 410, an apparatus may enable aspects related to random access.As described in greater detail above, the ULTR may be configured toassign/allocate RUs for random access (e.g., for simultaneous/concurrentUL transmissions by a plurality of STAs). In some aspects, afterreceiving an ULTR (e.g., DL transmission(s) 232, 234), an STA (e.g.,STA₁ 114) may determine the number (e.g., quantity, amount, extent,size, and/or any other suitable measurement) of the RUs assigned by theULTR for random access. For example, the STA (e.g., STA₁ 114) maydetermine the number of RUs assigned to it by utilizing theabove-described portion of the ULTR that includes a plurality ofuser-specific fields indicating a description of resource allocation forsimultaneous/concurrent UL transmissions by the plurality of STAs. TheSTA (e.g., STA₁ 114) may reduce a back-off counter based on the numberof RUs assigned by the ULTR for random access. In some aspects, reducingthe back-off counter based on the number of RUs assigned for randomaccess by the ULTR includes reducing a value of the back-off counter bya predetermined amount for each of at least one resource for randomaccess assigned by the ULTR and associated with a particular identifier.For example, if STA₁ 114 is assigned three RUs and its back-off counterwas initially set to a value of five, then the STA₁ 114 may decrementits back-off counter by three units, resulting in its reduced back-offcounter having a value of two.

Depending on a value of the reduced back-off counter, the STA (e.g.,STA₁ 114) may randomly select one or more of the RUs assigned for randomaccess by the ULTR. When the value of the reduced back-off counterreaches or crosses a threshold value, then that STA may randomly selectRUs assigned for random access. For example, if such a threshold valueis two (or greater), then STA₁ 114 may randomly select RUs assigned forrandom access; otherwise, STA₁ 114 may refrain from randomly selectingRUs for random access. Depending on a value of the reduced back-offcounter (e.g., if/when the value of the reduced back-off counter reachesor crosses a threshold value), the STA (e.g., STA₁ 114) may transmit aframe, packet, and/or data unit (e.g., UL transmission(s) 262, 264)using the randomly selected one or more RUs assigned by the ULTR forrandom access.

As described above, an ULTR may sometimes indicate various resourcesand/or resource units (e.g., RUs) that are allocated for random access.In other words, the ULTR may allocate various resources (e.g., RUs) forrandom access. Some systems may rely on random selection procedures tofairly allocate such resources to a plurality of RXs/STAsseeking/needing such resources. However, this may lead to unnecessarycontention, possible collisions, and overall inefficiencies in certaincircumstances.

In some configurations, an apparatus (e.g., TX/AP) may transmit an ULTR,wherein the ULTR is configured to assign/allocate at least one resource(e.g., RU) for random access. In some configurations, an apparatus(e.g., RX/STA) may receive an ULTR, wherein the ULTR is configured toassign/allocate at least one resource (e.g., RU) for random access. Insuch configurations, the apparatus (e.g., RX/STA) may determine anumber/amount/duration/size of the at least one resource (e.g., RU) forrandom access. In such configurations, the apparatus (e.g., RX/STA) mayreduce/adjust/decrement a back-off counter/back-off timer based on thedetermined number/amount/duration/size of the at least one resource(e.g., RU) for random access. In such configurations, the apparatus(e.g., RX/STA) may, if the reduced/adjusted/decremented back-offcounter/back-off timer has a value equal to or less than zero, refrainfrom (randomly) selecting one or more of the at least one resource forrandom access. In such configurations, the apparatus (e.g., RX/STA) may,if the reduced/adjusted/decremented back-off counter/back-off timer hasa value greater than zero, (randomly) select one or more of the at leastone resource for random access and transmit aframe/packet/data/information using/utilizing the selected one or moreof the at least one resource for random access.

In some configurations, reducing/adjusting/decrementing a back-offcounter/back-off timer based on the determinednumber/amount/duration/size of the at least one resource (e.g., RU) forrandom access may include reducing/adjusting/decrementing the back-offcounter/back-off timer by an amount oftime/quantity/duration/count-value equal/correspond/associated to/withthe determined number/amount/duration/size of the at least one resourcefor random access (as assigned/allocated by the ULTR). In someconfigurations, reducing/adjusting/decrementing a back-offcounter/back-off timer based on the determinednumber/amount/duration/size of the at least one resource (e.g., RU) forrandom access may include reducing/adjusting/decrementing a value of theback-off counter/back-off timer by a value offixed/predetermined/variable value/amount for each of the determinednumber/amount/duration/size of the at least one resource for randomaccess (as assigned/allocated by the ULTR). In some configurations, atleast one of (or each of) the at least one resource assigned/allocatedby the ULTR for random access is assigned/allocated/having a particularidentifier, wherein the apparatus (e.g., RX/STA) uses/utilizes thatparticular identifier to determine which of the resourcesassigned/allocated by the ULTR is the at least one resource for randomaccess. In some configurations, at least one resource (e.g., RU) forrandom access includes/means at least one resource (e.g., RU) that isnot assigned/allocated to a specific receiver/RX/STA/destination (by theULTR). In some configurations, at least one resource (e.g., RU) forrandom access includes/means at least one resource (e.g., RU) that isassigned/associated with a specific/particular/predetermined identifier(e.g., AID).

In some circumstances, an apparatus may benefit from remaining in apower-save/low-power mode for a particular period of time. For example,an RX/STA may benefit from remaining in a power-save/low-power modeuntil an ULTR is received. As described above, the ULTR mayallocate/assign at least one resource (e.g., RU) for random access. Insome circumstances, a system may benefit by reducing and/or minimizingoverhead in/during wireless communication. For example, scheduling everysingle ULTR may add substantial overhead to the system, thereby possiblyreducing the system efficiency and overall system throughput.

In some configurations, rather than scheduling each and every ULTR, atleast some ULTR may be communicated in a cascaded sequence of ULTR forrandom access. For example, a first set of one or more ULTRs may bescheduled and a second set of one or more ULTR may be cascaded after thefirst set of the one or more scheduled ULTRs. In some configurations, asignal communicated prior to the communication of the first set of theone or more scheduled ULTRs may indicate that a subsequent/next ULTR isa scheduled ULTR. Such a signal may be included in a beacon, a beaconframe, a header of another frame/packet, or in any other suitablesignal. Such a signal may also indicate a beginning of a transmissiontime, a start of a transmission time interval, a commencement of a TXOP,a target transmission time, and/or a desired transmissionperiod/duration for at least one of the first set of the one or morescheduled ULTRs. In some configurations, a scheduled ULTR may indicatethat a subsequent ULTR is a non-scheduled and/or cascaded/cascadingULTR. Such an indication may be a bit, sequence of bits, header field,and/or any other indicator included in the scheduled ULTR.

In some configurations, an apparatus (e.g., TX/AP) may transmit a firstsignal/message (e.g., beacon) comprising scheduling information, a starttime, and/or a time interval associated with at least a first ULTRconfigured to assign/allocate at least one resource for random access.In some configurations, an apparatus (e.g., TX/AP) may also transmit thefirst ULTR according to the scheduling information, start time, and/ortime interval, wherein the first ULTR includes an indication of acascaded sequence (of one or more other ULTRs) when one or more otherULTRs are set/scheduled for (subsequent) transmission. In someconfigurations, an apparatus (e.g., TX/AP) may also transmit anACK/NACK/BA after receiving data on the at least one resource for randomaccess. In some configurations, an apparatus (e.g., TX/AP) may alsotransmit one or more other ULTRs after transmitting the ACK/NACK/BA whenthe first ULTR includes the indication of the cascaded sequence (of oneor more other ULTRs).

In some configurations, an apparatus (e.g., RX/STA) may receive asignal/message (e.g., beacon) comprising scheduling information, a starttime, a time interval associated with at least a first ULTR configuredto assign/allocate at least one resource for random access. In someconfigurations, an apparatus (e.g., RX/STA) may also enter a low-powermode, a power-save mode, an ultra-low-power mode, a doze mode, and/or adoze-off mode until a time corresponding to the scheduling information,the start time, and/or the time interval included in the receivedsignal/message. In some configurations, an apparatus (e.g., RX/STA) maydetect and/or attempt to (randomly) select at least one resource forrandom access allocated/assigned by the first ULTR. In someconfigurations, an apparatus (e.g., RX/STA) may, if/when the attempt to(randomly) select at least one resource for random access isunsuccessful, determine/detect whether the first ULTR includes anindication of a cascaded sequence (of one or more other ULTRs). In someconfigurations, an apparatus (e.g., RX/STA) may receive a second ULTRand/or attempt to (randomly) select at least one resource for randomaccess when the first ULTR includes the indication of a cascadedsequence (of one or more other ULTRs). In some configurations, anapparatus (e.g., RX/STA) may detect and/or attempt to (randomly) selectat least one resource for random access allocated/assigned by the secondULTR if/when the attempt to (randomly) select the at least one resourcefor random access assigned/allocated in/by the first ULTR isunsuccessful.

At block 412, an apparatus may enable aspects related to performing ULcommunication(s). In some aspects, in response to receiving the ULTR(e.g., DL transmission(s) 232, 234), an STA may transmit an ULtransmission (e.g., UL transmission(s) 262, 264) (at least partially)simultaneously/concurrently with (UL transmission(s) of) one or moreSTAs of the plurality of STAs. That is, in response to transmitting theULTR, an AP may receive UL transmission(s) simultaneously/concurrentlyfrom a plurality of STAs. For example, referring to FIG. 2, at timeT_(vii), in response to receiving an ULTR (e.g., DL transmission 232,234), STA₁ 114, STA₂ 116 may simultaneously/concurrently transmit theirrespective UL transmission (e.g., UL transmission(s) 262, 264,respectively). In some aspects, receiving the DL multiuser transmission(e.g., DL multiuser transmission(s) 222 at time T_(iii)) andtransmitting the simultaneous/concurrent UL transmissions (e.g., ULtransmission(s) at time T_(vii)) by the plurality of STAs occur in thesame transmission opportunity.

In some aspects, as described above, an STA may determine the amount ofpower loss during the DL transmission of the ULTR (e.g., DLtransmission(s) 232, 234) from an AP to the STA. As also describedabove, in some aspects, the ULTR (e.g., DL transmission(s) 232, 234) mayinclude information corresponding to the power measurement of thetransmitted ULTR (e.g., DL transmission(s) 232, 234). In some aspects,based on the determined amount of power loss during the DL transmissionof the ULTR (e.g., DL transmission(s) 232, 234) from the AP to the STAand/or based on the target received signal strength (as included in theULTR), the STA may determine an amount of power (to be utilized by oneor more antennas) for the UL transmission (e.g., UL transmission(s) 262,264) by the STA to the AP. In accordance with the determined amount ofpower for the UL transmission, the STA(s) may transmit the ULtransmission(s) (e.g., UL transmission(s) 262, 264) to the AP. In someaspects, the UL transmission(s) may include information corresponding tohow much transmission power the STA(s) remains capable of using relativeto a transmission power currently utilized. For example, an ULtransmission 262 may include information indicating how much more powerSTA₁ 114 is able of using relative to how much power STA₁ 114 iscurrently using for that UL transmission 262. In some aspects, how muchtransmission power the STA remains capable of using relative to thetransmission power currently utilized refers to a difference between amaximum transmission power (of the STA(s)) and a currently utilizedamount of power (by the STA) for the UL transmission(s) (ULtransmission(s) 262, 264).

In some aspects, an AP may transmit and/or an STA may receive a requestfor simultaneous transmission of an acknowledgement message by theplurality of STAs. For example, referring to FIG. 2, in the DLtransmission(s) 222 at time T_(iii), or in the DL transmission(s) 232,234 at time T_(iv), AP₁ 112 may transmit and/or STA₁ 114, STA₂ 116 mayreceive a request for simultaneous transmission of an acknowledgementmessage by the plurality of STAs (e.g., STA₁ 114, STA₂ 116). In responseto the received request, an AP may receive and/or an STA may transmit anUL acknowledgement message simultaneously/concurrently with another STAof the plurality of STAs. For example, referring to FIG. 2, in the ULtransmission(s) 262, 264 at time T_(vii), the plurality of STAs (e.g.,STA₁ 114, STA₂ 116) may simultaneously/concurrently transmit an ULacknowledgement message to AP₁ 112 (e.g., in UL transmission(s) 262,264). In some aspects, in response to receiving the ULTR (e.g., DLtransmission(s) 232, 234), an STA may transmit and/or an AP may receivea feedback frame at a same time as a transmission of a feedback frame byanother STA. For example, referring to FIG. 2, at time T_(vii), inresponse to receiving a DL transmission 232 (e.g., ULTR) at time T_(iv),STA₁ 114 may transmit an UL transmission 262. The UL transmission 262may include a feedback frame and may be transmittedsimultaneously/concurrently with a transmission of a feedback frame inanother UL transmission 264 by STA₂ 116 to AP₁ 112.

It will be understood by one of ordinary skill in the art that thespecific order or hierarchy of the processes disclosed herein isprovided for illustrative and exemplary purposes. Based upon designpreferences, the specific order or hierarchy of steps in the processesmay be re-arranged and/or some processes may be combined or omittedwithout deviating from the scope of the present disclosure. Theaccompanying claims present elements of the various steps in a sampleorder, and are not meant to be limited to the specific order orhierarchy presented. The particular order, sequence, chronology, and/orcombination of the aspects described herein are not intended to limitthe scope of the present disclosure nor any aspect of the claims, unlessexplicitly required by the claims. Any of the aspects described hereinmay be configured or implemented in additional or alternative orders,sequences, chronologies, and/or combinations without deviating from thescope of the present disclosure. Each and every aspect described hereinis not necessarily required in all configurations and embodiments of thepresent disclosure. Accordingly, any aspect not recited or otherwiserequired by the claims shall not be construed as limiting the scope ofthe claims. That is, the scope of the claims shall not be construed anymore narrowly than required by the claims simply because there may exista possibility of any additional and/or alternative aspects describedthroughout the present disclosure. The scope of the claims shall not beconstrued as limited to the examples provided herein, unless acorresponding feature is expressly recited in the claims.

FIG. 5 is a block diagram 500 illustrating a non-limiting example of anAP (e.g., AP₁ 112) according to some aspects of the present disclosure.The AP may have various circuits, algorithms, hardware components,software modules, and/or computer-readable medium storingcomputer-executable instructions comprising various algorithms, any ofthe foregoing of which, individually or in some combination, may providethe structure corresponding to the means for performing any one or moreof the functions, features, steps, elements, methods, and/or operationsdescribed throughout the present disclosure.

The AP may include a bus 506. The bus 506 may include any number ofinterconnecting buses and/or bridges depending on the particular designof the AP. The bus 506 may provide a connection/link between variousaspects of the AP, which may include one or more of the following:processor(s) 550, computer-readable medium 540, memory 530, userinterface 510, bus interface 520, transceiver 504, and/or antenna(s)502. The bus 506 may enable a link between/to various other aspects,such as timing sources, peripherals, voltage regulators, and/or powermanagement circuits. The user interface 510 may exchange data via thebus interface 520. The bus interface 520 may provide an interfacebetween the bus 506 and the transceiver 504. The transceiver 504 may beconnected to one or more antennas 502. The transceiver 504 may provide ameans for wirelessly communicating (e.g., receiving data and/ortransmitting data) with various other apparatus over a wirelesstransmission medium. In some aspects, the transceiver 504 may receive asignal from the one or more antennas 502, extract information from thereceived signal, and provide the extracted information to theprocessor(s) 550. In some aspects, the transceiver 504 may receiveinformation from the processor(s) 550 and, based on the receivedinformation, generate a signal to be applied to the one or more antennas502. The memory 530 may include various information/data 532 related toany one or more of the functions, features, steps, methods, processes,and/or operations described herein.

The processor(s) 550 may include one or more circuits configured toenable, may perform one or more algorithms related to, and/or mayprovide the structure (e.g., means for) corresponding to any one or moreof the functions, features, steps, methods, processes, and/or operationsdescribed herein. In some aspects, the reception circuit/algorithm 551may provide the structure (e.g., means for) corresponding to any one ormore of the functions, features, steps, methods, processes, and/oroperations described herein with relation to receiving anything. In someaspects, the processing circuit/algorithm 552 may provide the structure(e.g., means for) corresponding to any one or more of the functions,features, steps, methods, processes, and/or operations described hereinwith relation to using anything, determining anything, consideringanything, refraining from considering anything, and/or randomlyselecting anything. In some aspects, the control circuit/algorithm 553may provide the structure (e.g., means for) corresponding to any one ormore of the functions, features, steps, methods, processes, and/oroperations described herein with relation to updating anything,refraining from updating anything, eliminating anything, overridinganything, maintaining anything, and/or entering into any mode. In someaspects, the transmission circuit/algorithm 554 may provide thestructure (e.g., means for) corresponding to any one or more of thefunctions, features, steps, methods, processes, and/or operationsdescribed herein with relation to generating anything and/ortransmitting anything. In some aspects, the othercircuit(s)/algorithm(s) 555 may provide the structure (e.g., means for)corresponding to any one or more of the other functions, features,steps, methods, processes, and/or operations described throughout thepresent disclosure. The processor(s) 550 may be responsible for generalprocessing, including the execution of software (e.g., instructions,code, algorithms, etc.) stored in/on the computer-readable medium 540.

The computer-readable medium 540 may be used for storing data that ismanipulated by the processor(s) 550. The computer-readable medium 540may be a non-transitory computer-readable medium. The computer-readablemedium 540 may include one or more instructions (e.g.,computer-executable code) configured to enable, may perform one or morealgorithms related to, and/or may provide the structure (e.g., meansfor) corresponding to any one or more of the functions, features, steps,methods, processes, and/or operations described herein. In some aspects,the reception instructions/algorithm 541 may provide the structure(e.g., means for) corresponding to any one or more of the functions,features, steps, methods, processes, and/or operations described hereinwith relation to receiving anything. In some aspects, the processinstructions/algorithm 542 may provide the structure (e.g., means for)corresponding to any one or more of the functions, features, steps,methods, processes, and/or operations described herein with relation tousing anything, determining anything, considering anything, refrainingfrom considering anything, and/or randomly selecting anything. In someaspects, the control instructions/algorithm 543 may provide thestructure (e.g., means for) corresponding to any one or more of thefunctions, features, steps, methods, processes, and/or operationsdescribed herein with relation to updating anything, eliminatinganything, overriding anything, maintaining anything, and/or enteringinto any mode. In some aspects, the transmission instructions/algorithm544 may provide the structure (e.g., means for) corresponding to any oneor more of the functions, features, steps, methods, processes, and/oroperations described herein with relation to generating anything and/ortransmitting anything. In some aspects, the othercircuit(s)/algorithm(s) 545 may provide the structure (e.g., means for)corresponding to any one or more of the other functions, features,steps, methods, processes, and/or operations described throughout thepresent disclosure. Additional details related to the aspects describedin FIG. 5 are provided throughout the present disclosure.

FIG. 6 is a block diagram 600 illustrating a non-limiting example of anSTA (e.g., STA₁ 114) according to some aspects of the presentdisclosure. The STA may have various circuits, algorithms, hardwarecomponents, software modules, and/or computer-readable medium storingcomputer-executable instructions comprising various algorithms, any ofthe foregoing of which, individually or in some combination, may providethe structure corresponding to the means for performing any one or moreof the functions, features, steps, elements, methods, and/or operationsdescribed throughout the present disclosure.

The STA may include a bus 606. The bus 606 may include any number ofinterconnecting buses and/or bridges depending on the particular designof the STA. The bus 606 may provide a connection/link between variousaspects of the STA, which may include one or more of the following:processor(s) 650, computer-readable medium 640, memory 630, userinterface 610, bus interface 620, transceiver 604, and/or antenna(s)602. The bus 606 may enable a link between/to various other aspects,such as timing sources, peripherals, voltage regulators, and/or powermanagement circuits. The user interface 610 may exchange data via thebus interface 620. The bus interface 620 may provide an interfacebetween the bus 606 and the transceiver 604. The transceiver 604 may beconnected to one or more antennas 602. The transceiver 604 may provide ameans for wirelessly communicating (e.g., receiving data and/ortransmitting data) with various other apparatus over a wirelesstransmission medium. In some aspects, the transceiver 604 may receive asignal from the one or more antennas 602, extract information from thereceived signal, and provide the extracted information to theprocessor(s) 650. In some aspects, the transceiver 604 may receiveinformation from the processor(s) 650 and, based on the receivedinformation, generate a signal to be applied to the one or more antennas602. The memory 630 may include various information/data 632 related toany one or more of the functions, features, steps, methods, processes,and/or operations described herein.

The processor(s) 650 may include one or more circuits configured toenable, may perform one or more algorithms related to, and/or mayprovide the structure (e.g., means for) corresponding to any one or moreof the functions, features, steps, methods, processes, and/or operationsdescribed herein. In some aspects, the reception circuit/algorithm 651may provide the structure (e.g., means for) corresponding to any one ormore of the functions, features, steps, methods, processes, and/oroperations described herein with relation to receiving anything. In someaspects, the processing circuit/algorithm 652 may provide the structure(e.g., means for) corresponding to any one or more of the functions,features, steps, methods, processes, and/or operations described hereinwith relation to using anything, determining anything, consideringanything, refraining from considering anything, and/or randomlyselecting anything. In some aspects, the control circuit/algorithm 653may provide the structure (e.g., means for) corresponding to any one ormore of the functions, features, steps, methods, processes, and/oroperations described herein with relation to updating anything,refraining from updating anything, eliminating anything, overridinganything, maintaining anything, and/or entering into any mode. In someaspects, the transmission circuit/algorithm 654 may provide thestructure (e.g., means for) corresponding to any one or more of thefunctions, features, steps, methods, processes, and/or operationsdescribed herein with relation to generating anything and/ortransmitting anything. In some aspects, the othercircuit(s)/algorithm(s) 655 may provide the structure (e.g., means for)corresponding to any one or more of the other functions, features,steps, methods, processes, and/or operations described throughout thepresent disclosure. The processor(s) 650 may be responsible for generalprocessing, including the execution of software (e.g., instructions,code, algorithms, etc.) stored in/on the computer-readable medium 640.

The computer-readable medium 640 may be used for storing data that ismanipulated by the processor(s) 650. The computer-readable medium 640may be a non-transitory computer-readable medium. The computer-readablemedium 640 may include one or more instructions (e.g.,computer-executable code) configured to enable, may perform one or morealgorithms related to, and/or may provide the structure (e.g., meansfor) corresponding to any one or more of the functions, features, steps,methods, processes, and/or operations described herein. In some aspects,the reception instructions/algorithm 641 may provide the structure(e.g., means for) corresponding to any one or more of the functions,features, steps, methods, processes, and/or operations described hereinwith relation to receiving anything. In some aspects, the processinstructions/algorithm 642 may provide the structure (e.g., means for)corresponding to any one or more of the functions, features, steps,methods, processes, and/or operations described herein with relation tousing anything, determining anything, considering anything, refrainingfrom considering anything, and/or randomly selecting anything. In someaspects, the control instructions/algorithm 643 may provide thestructure (e.g., means for) corresponding to any one or more of thefunctions, features, steps, methods, processes, and/or operationsdescribed herein with relation to updating anything, eliminatinganything, overriding anything, maintaining anything, and/or enteringinto any mode. In some aspects, the transmission instructions/algorithm644 may provide the structure (e.g., means for) corresponding to any oneor more of the functions, features, steps, methods, processes, and/oroperations described herein with relation to generating anything and/ortransmitting anything. In some aspects, the othercircuit(s)/algorithm(s) 645 may provide the structure (e.g., means for)corresponding to any one or more of the other functions, features,steps, methods, processes, and/or operations described throughout thepresent disclosure. Additional details related to the aspects describedin FIG. 6 are provided throughout the present disclosure.

Several aspects of communication systems are presented herein withreference to various apparatuses, methods, and computer-readable medium,which are described herein and possibly illustrated in the accompanyingdrawings by various blocks, modules, components, circuits, steps,processes, algorithms, etc. (collectively, “elements”). Such elementsmay be implemented using electronic hardware, computer software, and/orany combination thereof. Whether such elements are implemented ashardware and/or software may depend upon the particular applicationand/or design constraints imposed on the overall communication system.

Examples of processors include microprocessors, microcontrollers,digital signal processors (DSPs), field programmable gate arrays(FPGAs), programmable logic devices (PLDs), state machines, gated logic,discrete hardware circuits, and other suitable hardware configured toperform the various functionality described throughout this disclosure.One or more processors in the processing system may execute software.Software shall be construed broadly to mean instructions, instructionsets, code, code segments, program code, programs, subprograms, softwaremodules, applications, software applications, software packages,routines, subroutines, objects, executables, threads of execution,procedures, functions, etc., whether referred to as software, firmware,middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more exemplary configurations, the functionsdescribed may be implemented in hardware, software, firmware, or anycombination thereof. If implemented in software, the functions may bestored on or encoded as one or more instructions or code on acomputer-readable medium. Computer-readable media includes computerstorage media. Computer storage media may be any available media thatcan be accessed by a computer. By way of example, and not limitation,such computer-readable media may comprise a random-access memory (RAM),a read-only memory (ROM), an electrically erasable programmable ROM(EEPROM), compact disk ROM (CD-ROM) or other optical disk storage,magnetic disk storage or other magnetic storage devices, or any othermedium that can be used to carry or store desired program code in theform of instructions or data structures and that can be accessed by acomputer. Combinations of the foregoing may also be included within thescope of computer-readable media. Also, combinations of the foregoingmay also be included within the scope of memory.

The terms and phrases utilized in the present disclosure may havevarious meanings, definitions, descriptions, characterizations,classifications, and/or other attributes that are understood by one ofordinary skill in the art and which are within the scope of the presentdisclosure. It would be impractical to explicitly elaborate upon everysingle term and/or phrase in the present disclosure, and one of ordinaryskill in the art will understand the meanings, definitions,descriptions, characterizations, classifications, and/or otherattributes of the terms and/or phrases in the present disclosure, evenif not explicitly elaborated upon. Nevertheless, for purposes ofillustration but not limitation, various non-limiting examples of somemeanings, definitions, descriptions, characterizations, classifications,and/or other attributes are provided herein with reference to some ofthose terms and/or phrases in the present disclosure. None of theseexamples are intended to limit the scope of such terms and/or phrases;accordingly, such terms and/or phrases may have additional oralternative meanings, definitions, descriptions, characterizations,classifications, and/or other attributes without necessarily deviatingfrom the scope of the present disclosure.

The term(s) ‘receive’ and/or ‘receiving’ (and similar terms) may includeacquiring, obtaining, collecting, analyzing, reading, processing,decoding, demodulating, deciphering, and/or various other suitableoperations, features, and/or functions. The term(s) ‘transmit’ and/or‘transmitting’ (and similar terms) may include generating, modulating,addressing, designating, encoding, processing, sending, broadcasting,conveying, relaying, transferring, transporting, channeling, forwarding,propagating, routing, and/or various other suitable operations,features, and/or functions. The terms(s) ‘refrain’ and/or ‘refraining’(and similar terms) may include abstaining, avoiding, resisting,forgoing, desisting, renouncing, restraining, forbearing, bypassing,withholding, omitting, not performing, and/or various other suitableoperations, features, and/or functions. The term(s) ‘consider’ and/or‘considering’ (and similar terms) may include reading, processing,analyzing, inspecting, acknowledging, looking at, reviewing, comparing,processing, checking, viewing, assessing, and/or various other suitableoperations, features, and/or functions. The term(s) ‘determine’ and/or‘determining’ (and similar terms) may include processing, calculating,electing, selecting, looking up, reading, computing, using, concluding,deciding, resolving, settling, deducing, inferring, deriving, obtaining,and/or various other suitable operations, features, and/or functions.The term(s) ‘use’ and/or ‘using’ (and similar terms) may includeutilizing, employing, exploiting, applying, basing upon, leveraging,working with, using to look up, using to determine, using to/forreference, processing, analyzing, looking at, and/or various othersuitable operations, features, and/or functions.

The term(s) ‘eliminate’ and/or ‘eliminating’ (and similar terms) mayinclude excluding, not considering, refraining from considering,disqualifying, ignoring, and/or various other suitable operations,features, and/or functions. The term(s) ‘select’ and/or ‘selecting’ (andsimilar terms) may include choosing, electing, appointing, allocating,designating, determining, deciding on, picking, using, utilizing,performing an operation (e.g., transmission/reception) using, and/orvarious other suitable operations, features, and/or functions. Theterm(s) ‘random’ and/or ‘randomly’ (and similar terms) may includearbitrarily, indiscriminately, incidentally, by chance, withoutallocation/assignment, without designation, haphazardly, and/or variousother suitable operations, features, and/or functions. The term(s)‘override’ and/or ‘overriding’ (and similar terms) may includereplacing, annulling, overwriting, superseding, canceling, replacing,and/or various other suitable operations, features, and/or functions.The term(s) ‘maintain’ and/or ‘maintaining’ (and similar terms) mayinclude using, considering, managing, utilizing, employing, supporting,enabling, accommodating, processing, sustaining, and/or various othersuitable operations, features, and/or functions. The term(s) ‘trigger’and/or ‘cause’ may include elicit, activate, start, initiate, bringabout, generate, produce, trigger, cause, prompt, provoke, lead to,result in, precipitate, evoke, incite, kickoff, motivate, make, and/orvarious other suitable operations, features, and/or functions. The term‘in response to’ may refer to an indirect or direct causal relationship,an association, a correspondence, a temporal relationship orassociation, and/or various other suitable attributes. For example, Xmay be in response to Y if/when X is indirectly or directly caused by Y,if/when the occurrence/existence of X is associated with theoccurrence/existence of Y, if/when the occurrence/existence of Xcorresponds to the occurrence/existence of Y, if/when theoccurrence/existence of X is within a particular period of time relativeto the occurrence/existence of Y, if/when X has various other suitableattributes in relation to Y.

In some aspects, a ‘NAV’ refers to a virtual carrier sensing mechanismthat may be utilized in various wireless communication protocols. Byusing virtual carrier sensing, the need for (physical/actual) carriersensing (e.g., energy detection or sensing on a channel or subchannel)may be minimized, reduced, and/or limited, which can contribute to powerconservation. In some aspects, a NAV may be an indicator maintained byeach STA, and the indicator may indicate time periods when transmissiononto a wireless communication medium is not, will not be, or should notbe initiated by the STA, even if the STA's clear channel assessmentsenses that the channel is may not be busy (e.g., is idle/available). Insome aspects, a NAV may be configured to regulate whether the STAaccesses a wireless communication medium, channel, and/or subchannelduring a period of time. In some aspects, a NAV may be thought of as acounter that counts backwards, wherein the wireless communicationmedium, channel, and/or subchannel is busy anytime that the counter hasa positive value, and wherein the wireless communication medium,channel, and/or subchannel is available (e.g., idle) anytime that thecounter does not have a positive value (e.g., has a value of zero). Anapparatus (e.g., STA) may receive, read, determine, obtain, recall,utilize, ascertain, and/or otherwise interface with such information. Insome aspects, such information may be received in a frame, packet,and/or data unit, as described in greater detail herein. Based on suchinformation, the apparatus (e.g., STA) may determine whether a wirelesscommunication medium, channel, and/or subchannel is available or busyduring a particular period/duration of time. The phrase ‘updating aNAV,’ ‘setting a parameter/setting of a NAV,’ ‘setting a NAV,’ and/orvarious other similar/related phrases may refer to various functions,features, and/or operations related to such information. For example,such phrases may generally refer to updating and/or setting theinformation related to the duration/period during which a wirelesscommunication medium, channel, and/or subchannel is busy or available.Various additional and alternative aspects related to the NAV arereadily understood by one of ordinary skill in the art and are withinthe scope of the present disclosure.

The term(s) ‘detection’ and/or ‘detecting’ may refer to thedetermination, conclusion, deduction, inference, and/or other suitableoperation/function that the characteristics associated with a particularsignal satisfy at least one criterion, threshold, requirement,condition, parameter, and/or setting. For example, at least a portion(e.g., a preamble) of a signal may be detected if the strength (e.g.,power) of the received signal satisfies a particular criterion,threshold, requirement, condition, parameter, and/or setting. The term‘time synchronization’ may refer to the temporal attribute,relationship, and/or correlation of certain occurrences. In someaspects, the time synchronization of simultaneous/concurrenttransmissions (e.g., by a plurality of STAs) may refer to the attribute,relationship, and/or correlation that those simultaneous/concurrenttransmissions begin at the same/similar time as, occur (at least inpart) concurrently with, and/or end at the same/similar time relative toeach other. In some aspects, the phrase ‘simultaneous UL transmissions’may refer to ‘an UL transmission (by an STA) simultaneously/concurrentlywith another UL transmission (by at least one other STA).’ The term(s)‘reduce’ and/or ‘reducing’ may include decreasing, subtracting,lessening, lowering, decrementing, scaling, scaling down, curtailing,adjusting, and/or various other suitable operations, features, and/orfunctions.

The term ‘plurality’ refers to ‘more than one’ (e.g., two or more).Although the term ‘plurality’ may refer to ‘all’ in some aspects, theterm ‘plurality’ may refer to ‘some but not all’ or ‘some but fewer thanall’ in some other aspects. Therefore, recitation of ‘plurality of STAs’refers to ‘two or more STAs’ but such recitation does not necessarilyrequire or necessitate each and every STA in every embodiment.Accordingly, in some aspects, ‘plurality’ may be interchangeable with‘more than one but fewer than all/every.’

In some aspects, the term(s) ‘communication,’ ‘transmission,’ ‘signal,’‘frame,’ ‘packet,’ ‘data unit,’ and/or various other similar terms maybe interchangeable with each other without deviating from the scope ofthe present disclosure. In some aspects, the term(s) ‘communication,’‘transmission,’ ‘signal,’ ‘frame,’ ‘packet,’ ‘data unit,’ ‘UL signal,’‘DL signal,’ ‘ULTR,’ ‘UL trigger,’ and/or various other similar termsmay refer to any form, grouping, and/or encapsulation of one or morebits, signals, waveforms, and/or data. In some aspects, such terms maybe interchangeable relative to each other without deviating from thescope of the present disclosure. Without deviating from the scope of thepresent disclosure, some of these terms may be referred to by variousother terms, such as a protocol data unit (e.g., a physical layerconvergence protocol (PLCP) protocol data unit (PPDU), a MAC protocoldata unit (MPDU)), a service data unit (e.g., a physical layer servicedata unit (PSDU), a MAC service data unit (MSDU)), and/or various othersuitable form, grouping, and/or encapsulation of one or more bits,signals, waveforms, and/or data.

In some aspects, the term ‘apparatus’ may refer to the singular form ofthe word (apparatus). In some aspects, the term ‘apparatus’ is notlimited to the singular form of the word (apparatus) and, thus,‘apparatus’ may refer to the singular form and/or the plural form of theword (apparatus) without deviating from the scope of the presentdisclosure. For example, in some aspects, ‘apparatus’ may beinterchangeable with ‘apparatuses,’ ‘one or more apparatus,’ and/or ‘oneor more apparatuses’ without deviating from the scope of the presentdisclosure. In some aspects, the term ‘medium’ may refer to the singularform of the word (medium). In some aspects, the term ‘medium’ is notlimited to the singular form of the word (medium) and, thus, ‘medium’may refer to the singular form and/or the plural form of the word(medium) without deviating from the scope of the present disclosure. Forexample, in some aspects, ‘medium’ may be interchangeable with‘mediums,’ ‘media,’ ‘one or more mediums,’ and/or ‘one or more media’without deviating from the scope of the present disclosure.

In some aspects, the terms ‘destined for’ and ‘intended for’ may beinterchangeable without deviating from the scope of the presentdisclosure. In some aspects, the terms ‘destined/intended for’ and‘destined/intended to’ may be interchangeable without deviating from thescope of the present disclosure. The coverage area of a particulartransmitter (e.g., AP, STA) may include many receivers (e.g., AP(s),STA(s)); however, in some aspects, not all of those receivers arenecessarily the intended receivers or destinations of every transmissionfrom that transmitter. For example, in some aspects, the transmitter maytransmit a transmission (e.g., signal, frame, packet, and/or data unit)that is destined/intended for no more than a subset (e.g., less than anentirety) of all receivers that happen to receive that transmission byvirtue of being within the coverage area of that particular transmitter.In some aspects, a transmission is ‘intended for’ or ‘destined for’ oneor more particular receivers when/if that transmitter intended for thattransmission to include at least some data and/or information forthat/those one or more particular receivers. For example, thetransmitter may include some type of identifier in that transmission forthat/those particular receivers to use in order to identify that theyare the intended recipients or destinations of at least a portion ofthat transmission. Accordingly, in some aspects, the terms ‘destinedfor’ and ‘intended for’ shall not necessarily mean every receiver thathappened to receive that particular transmission, unless every receiverwas an intended recipient or destination of that particulartransmission.

The term(s) ‘field’ and/or ‘portion’ (and similar terms) may refer to asubset (e.g., not an entirety) of all of the data and/or informationcontained in an encapsulation sometimes referred to as a frame, packet,or data unit. A frame, packet, and/or data unit may include one or morefields and/or one or more portions. Each field and/or each portion maybe configured to include various types and forms of data and/orinformation without deviating from the scope of the present disclosure.

The term ‘STS’ may refer to spatial streams, bit streams, informationstreams, data streams, and/or streams of data and/or information thatmay have a time component and/or a frequency component. In some aspects,an STS may refer to a stream of modulated symbols created by applying acombination of spatial and temporal processing to one or more spatialstreams of modulated symbols. In some aspects, an STS may refer to oneof several streams of bits and/or modulated symbols that might betransmitted over multiple spatial dimensions that are created by the useof multiple antennas at both ends of a communication link. In someaspects, STS(s) may be generated using spatial multiplexing, which mayrefer to a transmission technique in which data streams are transmittedon multiple spatial channels that are provided through the use ofmultiple antennas at the transmitted and the receiver. In some aspects,a frame, packet, and/or data unit may include a plurality of STSs, andeach STS may be independently and/or separately encoded. STSs may employtime multiplexing and/or frequency multiplexing.

The term ‘number’ (e.g., ‘number’ of STSs) may refer to the quantity,numerical quantification, count, amount, size, extent, and various othersuitable measurements of the STSs. Because a frame, packet, and/or dataunit may include a plurality of STS, not all of which may bedestined/intended for a single STA, an STA that receives such a frame,packet, and/or data unit may select the STS(s) destined/intended for it.In some aspects, the term ‘variable’ refers to something that may beadjustable, changeable, configurable, flexible, and/or may consist of arange or set of potential, possible, or candidate values. The term(s)‘selection’ and/or ‘selecting’ (e.g., ‘selecting’ of one or more STSsincluded in a frame, packet, and/or data unit) may refer to identifying,electing, picking, and/or choosing of the specific STSsdestined/intended for a particular STS.

The term(s) ‘UP’ and/or ‘UP value’ may refer to an identifier,attribute, assignment, and/or allocation given to a particular user,STA, group of users, group of STAs, and/or other suitable destinationsto which a frame, packet, and/or data unit may be destined/intended. A‘user’ may be any intended destination or apparatus configured toutilize the information and/or data included in the frame, packet,and/or data unit. The UP of the STA(s)/user(s) may correspond to, may beassociated with, and/or may correlate with a UP of the frame, packet,and/or data unit.

In some aspects, the terms ‘assign,’ ‘assignment,’ and/or ‘assigned’ maybe interchangeable with ‘allocate,’ ‘allocation,’ and/or ‘allocated’without deviating from the scope of the present disclosure. In someaspects, the terms ‘duration,’ ‘length,’ ‘size,’ ‘period,’ and similarterms may be interchangeable without deviating from the scope of thepresent disclosure. In some aspects, the terms ‘simultaneous,’‘concurrent,’ and similar terms may be interchangeable without deviatingfrom the scope of the present disclosure. In the context of wirelesscommunication (e.g., reception and/or transmission), two signals,frames, packets, and/or data units may be characterized as‘simultaneous’ and/or ‘concurrent’ if they occur (at least in part) atthe same or substantially similar (e.g., temporally similar orcorrelated) times (i.e., even if not at the exact same time) relative toeach other.

In some aspects, the terms ‘resource(s)’ and ‘RU’ may be interchangeablewithout deviating from the scope of the present disclosure and may referto a duration of time and/or a range of frequencies (e.g., bandwidth)assigned, allocated, dedicated, scheduled, and/or otherwise earmarkedfor use by one or more apparatuses. In some aspects, one or moreresources/RUs may be configured for random access. Suchresource(s)/RU(s) may refer to resources shared by a plurality of STAs.In some aspects, the STAs may randomly select one or more of suchresource(s)/RU(s) for accessing the wireless communication channel orsubchannel.

In some aspects, the phrase ‘backoff counter’ may refer to a timer orcounter that counts or keeps track of an amount of time before anapparatus (e.g., STA) is allowed/permitted to perform anoperation/function. For example, an STA may have a backoff counter thatmay count backwards from a particular value (e.g., Time_(X), Xtime-units, etc.) until another particular value (e.g., Time_(Y), Ytime-units, etc., wherein Y<X in this example), at which time the STAmay perform a particular operation/function (e.g., utilize certainresources of a wireless communication channel). The term ‘transmissionopportunity’ may refer to an interval of time during which an STA ispermitted/allowed to access the wireless medium and/or communicate usinga particular wireless communication channel or subchannel. In someaspects, a transmission opportunity is defined by a starting time and amaximum duration.

In some aspects, the term(s) ‘acknowledgement’ and/or ‘acknowledgementmessage’ may include a positive acknowledgement message/signal and/or anegative acknowledgement message/signal, and/or may be a blockacknowledgement message/signal. The phrase ‘feedback frame’ may refer toany signal, frame, packet, and/or data unit that includes at least somefeedback information and/or data, such as a feedback matrix. A feedbackmatrix may include information about a signal received at areceiver/beamformee (e.g., STA), and such information may becommunicated from the receiver/beamformee (e.g., STA) to atransmitter/beamformer (e.g., AP). In some aspects, the term‘difference’ may refer to a subtraction between two values, fields,and/or other suitable aspects, but the ordering can be re-arrangedwithout deviating from the scope of the present disclosure. In someaspects, a difference between X and Y can mean X minus Y. In someaspects, a difference between X and Y can mean Y minus X. In someaspects, the phrase ‘originating from’ may refer to the origin of atransmission (e.g., an AP/STA from which a transmission originated),without regard to any relays that may extend the coverage area,communication range, and/or propagation distance of that transmissionfrom its origin.

The term(s) ‘protect’ and/or ‘protection’ may refer to maintaining awireless communication channel or subchannel, idle, unencumbered,utilized, reserved, available and/or otherwise accessible for aparticular communication during a particular duration or period of time.A transmission configured to cause a plurality of STAs to simultaneouslytransmit a signal/transmission that is configured to protect a DLmultiuser transmission to the plurality of STAs may referred to as arequest-to-send message/signal. A signal/transmission that is configuredto protect a DL multiuser transmission may be referred to as aclear-to-send message/signal. The term(s) ‘transmission power’ and/or‘transmit power’ may refer to the amount of power with which a signal,frame, packet, and/or data unit is transmitted. In some aspects, howmuch transmission power an apparatus (e.g., STA, AP, etc.) remainscapable of using relative to the transmission power currently/recentlyutilized may be referred to as transmit power margin/headroom. The term‘indication(s)’ may refer to a bit, a field, a parameter, a bitstream, amodulation, and/or any other suitable indicia. The terms ‘channel(s)’and/or ‘subchannel(s)’ may include or refer to a carrier, a subcarrier,a bandwidth, a portion of a bandwidth, a frequency range, a set offrequency values, and/or various other characteristics and attributesknown to one of ordinary skill in the art. The term ‘BSS’ may refer to aset of one or more STAs. Such STAs may be synchronized some of theiroperations with one another, such as the timings of their transmissions,receptions, NAVs, and/or any other suitable aspects.

Without deviating from the scope of the present disclosure, any aspectdescribed herein with respect to an AP may (or may not) apply to an STAand that the features described herein with respect to an STA may (ormay not) apply to an AP. Aspects disclosed herein with respect to an APand/or STA are hereby also disclosed with respect to any apparatus,method, and/or computer-readable medium that is configured in accordancewith such aspects.

The word “example” or “exemplary” may be used herein to mean “serving asa non-limiting example, instance, or illustration.” Any aspect,embodiment, and/or configuration described herein as “exemplary” or an“example” shall not necessarily be construed as preferred oradvantageous over other aspects, configurations, and/or configurations.The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any aspect described herein as “exemplary”is not necessarily to be construed as preferred or advantageous overother aspects.” Unless specifically stated otherwise, the term “some”refers to one or more. Combinations such as “A, B, and/or C,” “at leastA, B, or C,” “at least one of A, B, or C,” “at least one of A, B, andC,” and “A, B, C, or any combination thereof” include any combination ofA, B, and/or C, which may include any one of the followingpossibilities: (i) one or more of A; (ii) one or more of B; (iii) one ormore of C; (iv) one or more of A and one or more of B; (v) one or moreof A and one or more of C; (vi) one or more of B and one or more of C;or (vii) one or more of A, one or more of B, and one or more of C.

The description set forth below in connection with the appended drawingsis intended as a description of various configurations and is notintended to represent the only configurations in which the conceptsdescribed herein may be practiced. All structural and functionalequivalents to the elements of the various aspects described throughoutthis disclosure that are known or later come to be known to those ofordinary skill in the art are expressly incorporated herein by referenceand may be encompassed by the claims. Moreover, nothing disclosed hereinis intended to be dedicated to the public regardless of whether suchdisclosure is explicitly recited in the claims. No claim element is tobe construed as a means plus function unless the element is expresslyrecited using the phrase “means for.” The description herein is providedto enable any person skilled in the art to practice the various aspectsdescribed herein. Without deviating from the scope of the presentdisclosure, various modifications to the foregoing aspects may bereadily apparent to those skilled in the art, and the generic principlesdefined herein may be applied to other aspects. Thus, the claims are notintended to be limited to the aspects described herein and/or shown inthe accompanying drawings. In the claims, any reference to an element inthe singular form is not intended to mean “one and only one” unlessspecifically so stated, but rather “one or more.”

1. A station (STA) configured for wireless communication, the STAcomprising: a transceiver configured to receive a downlink (DL)transmission comprising a packet destined to a plurality of STAs; andone or more processors configured to: determine whether a portion of aheader of the received packet is repeated at least once, determine thatthe data packet is a legacy data packet if the portion of the header isnot repeated at least once, and determine that the data packet is not alegacy data packet if the portion of the header is repeated at leastonce; use a field included in the packet to determine a total number ofspace-time streams (STSs) included in the packet and further use thefield to select a subset of values from a set of values indicating anumber of STSs destined to each of at least some of the plurality ofSTAs; and determine a value of a user position (UP) assigned to the STAand select which of the plurality of STSs in the packet are destined tothe STA by considering a number of STSs allocated to one or more otherSTAs each assigned a UP value that is different from the UP valueassigned to the STA, wherein the transceiver is further configured toreceive, from an access point (AP), an uplink (UL) transmission request(ULTR) configured to trigger simultaneous UL transmissions by theplurality of STAs within a period of time after receiving the ULTR,wherein the ULTR comprises a first portion including a field common tothe plurality of STAs and indicating a duration of at least a portion ofthe simultaneous UL transmissions, wherein the ULTR further comprisesinformation for identifying the plurality of STAs for the simultaneousUL transmissions, wherein the transceiver is further configured totransmit the UL transmission in response to receiving the ULTR.
 2. TheSTA of claim 1, wherein the transceiver is further configured to receivea signal configured to cause a plurality of STAs to simultaneouslytransmit a signal configured to protect a DL multi-user transmission. 3.The STA of claim 2, wherein the received signal includes an indicationthat identifies each of the plurality of STAs, and wherein a timesynchronization among the plurality of RXs transmitting the signalconfigured to protect the DL multi-user transmission is based on an endtime of the received signal configured to cause the plurality of STAs tosimultaneously transmit the signal configured to protect the DLmulti-user transmission.
 4. The STA of claim 1, wherein the portion ofthe header comprises at least one of a short training field (STF), along training field (STF), or a signal field (SIG), a non-highthroughput signal field (L-SIG), a Signal A field (SIG-A), or a Signal Bfield (SIG-B).
 5. The STA of claim 1, wherein: the transceiver isfurther configured to receive a frame from a second STA different fromthe STA and the AP; and the one or more processors is/are furtherconfigured to use the received frame to set a network/navigationallocation vector (NAV) of the STA, and to refrain from considering theNAV of the STA in response to receiving the ULTR when the second STA isin a same basic service set (BSS) as the STA.
 6. The STA of claim 1,wherein the one or more processors is/are further configured todetermine not to reset one or more parameters corresponding to apreceding network allocation vector update caused by an apparatus withwhich the STA is associated, when the transceiver receives, from anoverlapping basic service set (BSS) apparatus, a message configured toor comprising information for early termination of a transmissionopportunity, wherein the overlapping BSS comprises a BSS with which theSTA is not associated.
 7. The STA of claim 6, wherein the ULTR furthercomprises a second portion including a plurality of user-specific fieldsindicating a description of resource allocation for the simultaneous ULtransmissions by the plurality of STAs, wherein the received messagecomprises a contention free end message.
 8. The STA of claim 1, whereinthe one or more processors is/are further configured to, in response toreceiving the ULTR, consider a network/navigation allocation vector(NAV) unless the NAV was set by a frame originating from an apparatusfrom which the ULTR was transmitted.
 9. The STA of claim 1, wherein thetransceiver is further configured to, in response to receiving the ULTR,transmit a frame without considering a navigation/network allocationvector (NAV) when a response to the ULTR comprises a blockacknowledgement and a duration of the UL transmission is below athreshold value.
 10. The STA of claim 1, wherein: the transceiver isfurther configured to receive a frame from a second STA different fromthe STA and the AP; and the one or more processors is/are furtherconfigured to use the received frame to set a network/navigationallocation vector (NAV) of the STA, and to refrain from considering theNAV of the STA in response to receiving the ULTR when a basic serviceset (BSS) identifier (BSSID) of a BSS with which the STA is associatedcorresponds to a BSSID of a BSS with which the second STA is associated.11. A non-transitory computer-readable medium comprising code orinstructions configured to cause a STA to: receive a downlink (DL)transmission comprising a packet destined to a plurality of STAs;determine whether a portion of a header of the received packet isrepeated at least once, determine that the data packet is a legacy datapacket if the portion of the header is not repeated at least once, anddetermine that the data packet is not a legacy data packet if theportion of the header is repeated at least once; use a field included inthe packet to determine a total number of space-time streams (STSs)included in the packet and further use the field to select a subset ofvalues from a set of values indicating a number of STSs destined to eachof at least some of the plurality of STAs; determine a value of a userposition (UP) assigned to the STA and select which of the plurality ofSTSs in the packet are destined to the STA by considering a number ofSTSs allocated to one or more other STAs each assigned a UP value thatis different from the UP value assigned to the STA; receive an uplink(UL) transmission request (ULTR) configured to trigger simultaneous ULtransmissions by the plurality of STAs within a period of time afterreceiving the ULTR, wherein the ULTR comprises a first portion includinga field common to the plurality of STAs and indicating a duration of atleast a portion of the simultaneous UL transmissions, wherein the ULTRfurther comprises information for identifying the plurality of STAs forthe simultaneous UL transmissions; and transmit the UL transmission inresponse to receiving the ULTR.
 12. The non-transitory computer-readablemedium of claim 11, wherein the code or instructions are furtherconfigured to cause the STA to receive a signal configured to cause aplurality of STAs to simultaneously transmit a signal configured toprotect a DL multi-user transmission.
 13. The non-transitorycomputer-readable medium of claim 12, wherein the received signalincludes an indication that identifies each of the plurality of STAs,and wherein a time synchronization among the plurality of RXstransmitting the signal configured to protect the DL multi-usertransmission is based on an end time of the received signal configuredto cause the plurality of STAs to simultaneously transmit the signalconfigured to protect the DL multi-user transmission.
 14. Thenon-transitory computer-readable medium of claim 11, wherein the code orinstructions are further configured to cause the STA to: receive a framefrom a second STA different from the STA and the AP; use the receivedframe to set a network/navigation allocation vector (NAV) of the STA;and refrain from considering the NAV of the STA in response to receivingthe ULTR when the second STA is in a same basic service set (BSS) as theSTA.
 15. The non-transitory computer-readable medium of claim 11,wherein the code or instructions are further configured to cause the STAto determine not to reset one or more parameters corresponding to apreceding network allocation vector update caused by an apparatus withwhich the STA is associated, when the STA receives, from an overlappingbasic service set (BSS) apparatus, a message configured to or comprisinginformation for early termination of a transmission opportunity, whereinthe overlapping BSS comprises a BSS with which the STA is notassociated.
 17. The non-transitory computer-readable medium of claim 15,wherein the ULTR further comprises a second portion including aplurality of user-specific fields indicating a description of resourceallocation for the simultaneous UL transmissions by the plurality ofSTAs, wherein the received message comprises a contention free endmessage.
 18. The non-transitory computer-readable medium of claim 11,wherein the code or instructions are further configured to cause the STAto, in response to receiving the ULTR, transmit a frame withoutconsidering a navigation/network allocation vector (NAV) when a responseto the ULTR comprises a block acknowledgement and a duration of the ULtransmission is below a threshold value.
 19. The non-transitorycomputer-readable medium of claim 1, wherein the code or instructionsare further configured to cause the STA to: receive a frame from asecond STA different from the STA and the AP; and use the received frameto set a network/navigation allocation vector (NAV) of the STA; refrainfrom considering the NAV of the STA in response to receiving the ULTRwhen a basic service set (BSS) identifier (BSSID) of a BSS with whichthe STA is associated corresponds to a BSSID of a BSS with which thesecond STA is associated.
 20. A method of wireless communication by astation (STA), the method comprising: receiving a downlink (DL)transmission comprising a packet destined to a plurality of STAs;determining whether a portion of a header of the received packet isrepeated at least once, determining that the data packet is a legacydata packet if the portion of the header is not repeated at least once,and determining that the data packet is not a legacy data packet if theportion of the header is repeated at least once; using a field includedin the packet to determine a total number of space-time streams (STSs)included in the packet and further use the field to select a subset ofvalues from a set of values indicating a number of STSs destined to eachof at least some of the plurality of STAs; determining a value of a userposition (UP) assigned to the STA and select which of the plurality ofSTSs in the packet are destined to the STA by considering a number ofSTSs allocated to one or more other STAs each assigned a UP value thatis different from the UP value assigned to the STA; receiving an uplink(UL) transmission request (ULTR) configured to trigger simultaneous ULtransmissions by the plurality of STAs within a period of time afterreceiving the ULTR, wherein the ULTR comprises a first portion includinga field common to the plurality of STAs and indicating a duration of atleast a portion of the simultaneous UL transmissions, wherein the ULTRfurther comprises information for identifying the plurality of STAs forthe simultaneous UL transmissions; and transmit the UL transmission inresponse to receiving the ULTR.